View & Create Cases from Jira Panel

AIO Tests offers integration points with Jira via the AIO Tests Jira Panel so that you can view traceability information of a Jira issue without leaving Jira. This article covers key features of the Jira Panel.

Enabling Jira Panel

AIO Tests Jira panel is enabled by default for all the issues of the project once the AIO Tests app is enabled for the project.

AIO Tests panel shows three tabs - Cases, Cycles and Impacted Executions along with a refresh button (highlighted). By default, the tab which has data is highlighted. If more than one tab has data, then the panel will land on Cases tab.

• Refresh: This button 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
  
  

  Open

  

   

• Cases: List of cases linked to the story for traceability is shown. The number next to the tab name represents the number of cases linked to the issue (discussed in detail below). 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 project are maintained separately then the test repository can be maintained in testing project but can be linked to stories in requirements project). If a case is linked to the issue to which the user doesn’t have access to then they only see the key of the linked case and a notification stating the reason

• Cycles: List of cycles where the issue is linked for traceability is shown. 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 cycles list if it has been linked using the option below while creating the cycle
  

  Open

  

   

• Impacted Executions: This tab will show data on Jira Defects. It shows cases against which the defect has been linked in AIO Tests. The grid shows title of the case, the cycle and run # in which the defect is linked, the reporter of the defect (case linked by), 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
  
  

Creating New Cases

The AIO Tests Jira panel offers an option to ‘Quick Create’ case from a Jira issue itself. The user has to enter minimum information and the case gets created in AIO Tests and also gets linked to the Jira issue automatically (if there are mandatory fields defined other than the minimum information showed on the panel, user will be prompted to enter details in a pop-up screen).

When no cases are linked to the Jira issue, below screen (on left) is displayed. The screen on the right gets displayed by clicking the ‘Create Case’ button.

Users need to enter the Title (the only mandatory field by default). They have the option to set the priority of the case (by default it will be ‘Not Assigned’) and the status (by default it will be ‘Published’) by clicking on the ‘Not Assigned’ and 'Published’ links. The Owner is set by default as the user creating the case. Users can enter additional details of a case using the expand icon. Once a case has been created, a new line appears for quickly adding another case as shown in the second image on the right. If mandatory fields are present, the create new case screen will pop-up and users will need to enter data for mandatory fields.

If cases are already linked to the Jira issue, then the ‘Create New Case’ link doesn’t appear. Users can create and link new cases using the top '+' icon.

Creating Cross-Project Linking

The project icon is displayed on the left of the Title box. By default the current Jira project icon is loaded allowing users to create cases in the current project. Users have the option to change the project by clicking the project icon. A list of Jira projects to which the user has access is shown and user can select another project.

Cross-project linking is helpful when users need to maintain a common test repository across multiple projects.

Linking Existing Cases

Existing AIO Cases can be linked to a Jira issue directly from AIO Tests Jira panel by clicking the link button highlighted below.

A search box opens up to allow searching for cases by case key, case title or case’s automation key. If users want to use additional filters to search for a case, they can do that by clicking on the highlighted filters icon. Users can link cases from other projects by selecting the desired Jira project from the Jira project icon.

On clicking any of the results from the search results drop-down, the case gets linked to the Jira issue with a success message. If a user doesn’t have access to the linked case of another project, only case key is shown along with a notification stating the reason.

Unlinking Cases

Cases linked for traceability to a Jira issue can also be unlinked from the AIO Tests Jira panel. Right-Click on the row of the case that needs to be unlinked to see the unlink option (highlighted below) or select the case using the checkbox and click Unlink button

A confirmation message appears on clicking the unlink icon and upon confirmation from the user, the case is unlinked from the Jira issue. Multiple cases can be unlinked together by checking the boxes on the left of the case key and clicking the Unlink option from the top.

For details on linking and unlinking Cycles to a Jira issue, please click here.

Viewing Case Executions

Users can view the last 3 executions of a case within a cycle from AIO Tests Jira Panel. The list is populated with 5 cycles. The criteria for determining the cycles is last 5 cycles in which the case was most recently updated or added. From Cases tab, right-click on the row of the case that needs to be reviewed and select ‘Executions’

The users will see the executions list as shown below. They can see the AIO case key, Jira’s project icon, option to “Quick Execute” the case and the Executions grid shows

• Cycle Key in which the case was updated/added

• Cycle Title in which the case was updated/added

• Assignee to whom the case has been assigned for execution

• Last 3 executions (runs) status of the case within the cycle

Key information about each status can be seen by hovering over the status icons. Users can see the

• Cycle key

• Run # (says latest execution for the most recent one along with the run#)

• Status (Passed, Failed, etc.)

• Created/Updated date

• Created/Updated by (user name)

Users can also update existing runs from Jira panel itself. Click on any of the status icons to see the screen below. It shows the AIO Case key → AIO Cycle key and the Run# at the top.

The highlighted buttons are all clickable.

• You can change the status of this run/case by clicking on the status icon

• You can see the defects attached to the case by clicking on the defects icon. You can also create new bug/story/issue from the defects screen

• You can see the comments attached to the case for this run

• You can see the attachments on this case, if any and also upload attachments from here

Executing a Single Case from Jira Issue

Users can execute a single case from the panel itself. Select ‘Quick Execute’ from the right-click of a case that needs to be executed.

The Quick Execute screen allows the user to

• Select the cycle and the project where the case should be executed - as part of an already created cycle or a new cycle

  • Existing cycle: the last cycle created in AIO tests is auto-populated. User has the option to remove the cycle and choose another existing cycle through a search box. The case will be added to the cycle if it is not present in the cycle or a new run will be created for the case in the specified cycle.

    • If the case is already present in the selected cycle and the version of the case has been changed since it was added to the cycle, users get the option to choose the version of the case that they want to add to the cycle (shown below)

       

       

  • New cycle: the screen is auto-populated with a cycle title if there are no mandatory fields for Cycle creation. User has the option to specify a title or use the given title. User can add more details by clicking on the expand icon. A new cycle will be created and the selected case will be added to the cycle. If mandatory fields have been specified for the cycle, user will be first asked to create a cycle and then execute the case in the newly created cycle (second screenshot)

     

     

     

     

• Set the status of the case (Passed, Failed, etc.)

On clicking Execute, a run is either created or added in the cycle, depending upon the user selection and the result is displayed as shown below.

From this screen, users can update the status again, if they wish to, add defects, comments and attachments (icons are clickable).

Executing Multiple Cases from Jira Issue

Users can also execute multiple cases from the panel. Select the cases that are in Published status and select ‘Quick Execute’ from the top ellipsis as shown below.

On clicking ‘Quick Execute’, the below screen is displayed.

The functionality of Existing/New cycle is same as single case execution. The status can also be updated from here. The screen below is displayed on click of Execute. The status, defects, comments and attachments can be updated for each case/run from the highlighted icons.

Adding Single & Multiple Cases to Cycle from Jira Issue

Users can also add case(s) to an existing cycle of projects they have access to for execution. Only Published cases can be added to a cycle. So the ‘Add to Cycle’ option doesn’t appear for cases in other statuses.

For multiple cases, an error is displayed asking user to only select Published cases.

On click of “Add to Cycle, a modal shows asking user to select the project and the cycle to which the case(s) need to be added. A case only gets added if it doesn’t already exist in the cycle. Users can add case(s) to multiple cycles.

Adding Single & Multiple Cases to Set from Jira Issue

Users can also add case(s) to an existing set of projects they have access to for execution. Only Published cases can be added to a set. So the ‘Add to Set’ option doesn’t appear for cases in other statuses.

For multiple cases, an error is displayed asking user to only select Published cases.

On click of “Add to Set, a modal shows asking user to select the project and the set to which the case(s) need to be added. A case only gets added if it doesn’t already exist in the set. Users can add case(s) to multiple sets.