AIO Tests offers integration points with Jira via the AIO Tests Jira Panel. With this feature, you can view traceability information of a Jira issue without leaving Jira.
By default, the AIO Tests Jira panel is enabled for all the issues of the project for which you have enabled the AIO Tests app.
In the Jira ticket, users can view three tabs in the AIO Tests panel- Cases, Cycles, and Impacted Executions.
By default, the tab which has data is highlighted. However, if more than one tab has data, then the panel will land on the Cases tab.
In the AIO Tests panel, there is a Refresh button that can be used to refresh the grids if linking/unlinking/creating of cases/cycles/defects is being done in another tab or by another user.
Cases: This tab shows the list of cases linked to the story for traceability. The number next to the Cases tab name represents the number of cases linked to the issue. Cases can be created in the project to which the issue belongs or in any other project thus letting users perform cross-project linking (e.g. if testing and requirements projects are maintained separately then the test repository can be maintained in the testing project but can be linked to stories in the requirements project). If a case is linked to the issue to which the user doesn’t have access then they only see the key of the linked case and a notification stating the reason.
Cycles: The Cycles tab shows the list of cycles where the issue is linked for traceability. The number next to the tab name represents the number of cycles linked to the issue (click here to learn more). The cycles listed here do not represent the cycles in which the linked cases are being executed. This tab only shows the cycle list if it has been linked using the option below while creating the cycle.
Impacted Executions: This tab shows data on Jira Defects. It shows cases against which the defect has been linked in AIO Tests. The grid shows the title of the case, the cycle and run # in which the defect is linked, the reporter of the defect (case linked by), the status of the case when the defect was reported and the latest status of the case in the cycle (which can be different if additional runs have been created since the defect was reported). The status columns on hover over also show the time when the defect was reported and the time of the current status too.
For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.