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.
On the AIO Tests Panel, users can view three tabs- Cases, Cycles, and Impacted Executions/Defects.
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.
If the issue type is not “Default Jira Issue Type for creating defects”, setting from General Preferences, or there are associated defects with the issue, then the AIO Tests Jira panel shows the Defects tab along with the Cases and Cycles. The AIO Tests Jira panel show the Impacted Executions tab only if there are impacted executions.
If the issue type is “Default Jira Issue Type for creating defects”, setting from General Preferences, or there are impacted runs, then the AIO Tests Jira panel shows the Impacted Executions tab along with the Cases and Cycles. The AIO Tests Jira panel shows the Defects tab only if there are defects associated with the issue.
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.
Defects: This tab shows all the defects associated with a user story via traceability. It also displays the defects from archived cases as well as cycles. The number next to the tab name represents the number of defects directly associated with the issue. On the defects section, users can view the defects' type, key, priority, status, title, and impacted executions. The priority columns, when hovered over, show the defect's severity. By clicking on the “view impacted executions”, users can view the cases that are associated with the story itself or the child. It will only display the impacted executions for those cases. For example, if it is a child issue, it will show cases that are directly associated with that particular child issue.
In the toolbar, there are two options are available to the user:
Show in Issue Navigator: By clicking on the Issue Navigator, users can view the associated bugs in Jira for further analysis.
Include Defects from Child Issues: By toggling on the “Include defects from child issues” option, users can view the defects associated with any child issues. There is also an indicator that shows whether the default issue is associated directly with itself or it is associated with a child issue. The blue indicator shows that the default issue is associated with itself, and the grey indicator shows that the defect issue is associated with the child issue.
Both the blue and grey indicators will be displayed if the default issue is associated with itself and the child issue.
For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.