Details
-
User Story
-
Resolution: Done
-
P2: Important
-
QSR 2.0
-
None
-
1
-
Sprint 2 Week15, Sprint 3 Week17, Sprint 4 Week19, Sprint 5 Week21, Sprint 6 Week23
Description
For the requirement traceability:
TestRail allows using the references to the Jira issues. That is handy for the Test Rail users who can also run a reference coverage report to see what references have been covered.
Well, it works in both ways. If there is a Jira issue that is referred from the Test Rail, the Jira can show the linked issue if the plugin is enabled.
In case we would transform all the requirements to the Jira items, we could easily see if those items are covered by the tests already in the Jira tool.
Since the Jira is used by the Qt community, the Jira admin required that the discussion for the use of the plugin is done in the community email list. That has been done a long time ago, and there were no responses, especially no objections. This means lazy approval.
So we could have the plugin enabled without further agreement ceremonies.
That would make the life easier. The use of the plugin has been piloted earlier in a copy of the Jira instance.
Definition of Done
- The plugin has been tested to be ok
- The plugin has been enabled by Jira admin
- The plugin has been configured for the QSR project
- The plugin shows correct data fromTestRail in Jira issue for linked tests
- The TestRail to Jira integration works without any interruption
- The corresponding confluence page has been updated
- The stakeholders have been informed