We are running the new integration at the moment - it’s pretty nice!
One thing I’d like to point out is that the naming of the “Defects” field on a test result is now a little bit unintuitive.
Consider the following workflow:
Tester is testing a new requirement
- Tester creates a new test case for the requirement, and fills in the Reference field, which points to the JIRA requirement. Tester saves the test case and adds it to a test plan / run.
- Tester runs through the test in TestRail, and marks it as a Pass
In order for the result to appear within the “For Tests” area of the JIRA item, the tester must manually fill in the JIRA item identifier in the Defects field.
a) It wouldn’t be a defect at this point, so the naming doesn’t make sense
b) It would be easier if this value was autopopulated from the Case.
Prior to getting to step 1 in the above example, it would also be good if you could see the untested state of the new test case from within JIRA.
One question that came up in a demonstration of the integration today was about the performance implications of the linkage - is the References field in a TestRail test case indexed?
Finally, we’re wondering if there is going to be a way to do the Requirement -> Test Cases coverage reports from within JIRA?