Note: Jira users possessing 'Administer Project' and 'Browse Projects' permissions for the project can access QMetry Project Settings.

Configure QMetry for Jira

Note:

• The mentioned settings are mandatory to start working on QMetry Test Management for Jira.

• For a team-managed project, if the Administrator does not have permission to the team-managed project (in case of private access) they will not be able to enable/disable the app.

Steps

1. Open the Projects drop-down on the main menu and select the Project to which you want to apply the QMetry settings.

2. Click on the Project Settings at the bottom left on the navigation bar.

Open

3. On the Project settings page, click on the QMetry Project Settings at the bottom left on the navigation bar.

Open

4. On the screen at the right, enable QMetry For Jira to start managing test cases.

Once you enable the QMetry For Jira option, you will be able to view QMetry for Jira features in the project.

Enable Issue Types for Story and Bug

The section becomes visible as soon as you enable the QMetry For Jira option. You can enable/disable Story and Bug Issue Types for particular issue types in Jira. Selected issue types will be considered as Story/Bug.

For example, Story and Epic are enabled as Story Issue Type. Then issues with "Story" and "Epic" type in Jira can be linked as Story in QMetry for Jira. In the same way, you can enable issue types for Bug.

This configuration at the Issue Type level is applicable to a particular project in Jira.

Note: Jira users with the “Administer Project” and “Browse Projects” permissions can access the settings page and configure QMetry for Jira features at the Issue Type level.

If enabled, the QMetry for Jira features will be available to use with that particular Issue Type in Jira. The Test Case/Acceptance Criteria panel will be visible below the Description section.

Steps

1. Open the Projects drop-down on the main menu and select the Project to which you want to apply the QMetry settings.

2. Click on the Project Settings at the bottom left on the navigation bar.

3. On the Project settings page, click on the QMetry Project Settings at the bottom left on the navigation bar.

4. On the screen at the right, enable QMetry For Jira to start managing test cases.

The section becomes visible as soon as you enable the QMetry For Jira option. You can enable/disable Story and Bug Issue Types for particular issue types in Jira.

This configuration at the Issue Type level is applicable to a particular project in Jira.

There are two tabs: Issue Type, BDD, and Email Notification.

On the Issue Type tab, there are two sections: Story and Bug.

→ Story: You can link only those issue types as Story which are enabled here. QMetry 'Test Case/Acceptance Criteria' panel will be available for enabled issues type(s) only.

By default, all issue types will be enabled. Select the issue type(s) that you want to disable for Story and click on the Apply Changes button.

Notes:

• Only enabled issue types will be allowed to link as a Story.

• QMetry Test Case/Acceptance Criteria panel will be shown for Jira issue pages with Enabled issue types only.

A. You can select individual issue types by clicking on the adjacent icon.

B. Select/deselect all issue types at once by clicking on Enable All/Disable All option.

C. If there is a long list of issue types, you can also search for a specific issue type with the help of a search box.

The confirmation message pops up. Click on the Apply Changes button to proceed.

→ Bug: You can link only those issue types as Bug which are enabled here. QMetry 'Traceability/Test Case' panel will be available for enabled issues type(s) only.

By default, all issue types will be enabled. Select the issue type(s) that you want to disable for Bug and click on the Apply Changes button.

Notes:

• Only enabled issue types will be allowed to link as a Bug.

• QMetry Bug Traceability/Test Case panel will be shown for Jira issue pages with Enabled issue types only.

A. You can select individual issue types by clicking on the adjacent icon.

B. Select/deselect all issue types at once by clicking on Enable All/Disable All option.

C. If there is a long list of issue types, you can also search for a specific issue type with the help of a search box.

The confirmation message pops up. Click on the Apply Changes button to proceed.

Once enabled, the QMetry for Jira features will be available to use within corresponding issue types in Jira. The Test Case/Acceptance Criteria panel is displayed below the Description section.

Disable Issue Types for Story and Bug

The screen displays the list of Issue Types with flags indicating whether the QMetry for Jira features is “Enabled” or “Disabled” for each Issue Type. It is a toggle option to Enable or Disable the feature.

If you disable the issue type for Story/Bug, users will not be allowed to link the disabled issue type as Story/Bug. The QMetry for Jira features will not be available for that particular Issue Type in Jira.

To disable the QMetry for Jira Features for a particular Issue Type, click on the enabled icon and click on the Apply Changes button. To disable all the enabled issue types click the Disable All option and click on the Apply Changes button. The confirmation message pops up.

Click the Disable button after reading the message. The QMetry for Jira Features turns disabled for the Issue Type.

The Test Case/Acceptance Criteria panel will not be visible below the Description section in Jira.

If the Issue Type is "Bug", then the Traceability tab will not be available in Jira.

Auto-link Execution Bugs to Stories

Admin can configure the option to auto-link bug(s) that are found during execution to the story with specific relation. If the option is enabled, bugs logged to a test case execution get automatically linked to the Jira story associated with the corresponding test case. The bugs are displayed under the Linked Issues section of the Jira story as per the relation defined in the configuration in Project Settings.

Use Case: During the process of marking the Story progress as Done, it is customary for the QA team and Managers to thoroughly assess all the bugs associated with the executed stories and ascertain whether they have been resolved. To facilitate this, it is of utmost importance to establish bug traceability for the stories identified during execution, allowing all QA teams to review them during sprint closure or triage discussions.

Once the settings are switched on, the newly created/linked bugs will be associated with the story.

Required Permissions:

The following Jira permissions are required:

• Browse project permission

• Link Issues permission

• issue-level security permission (Only if issue security schemes are configured in Jira)

Notes:

• Admin can configure settings to enable/disable auto-linking of bugs to the story. The option remains enabled by default for new projects.

• Admin can also choose the relation of the bug with Jira Story. The default relation is “Relates to”.

• If the same bug is logged from different test cases which are linked to the same story, the bug will be linked only once to the story under one relationship. If the relation is changed under the Auto link configuration in Project Settings, then the bugs logged after that will be linked to the story under that changed relation.

• If an individual bug is linked with the test case execution and test step execution, the bug will be linked only once to the story.

• If a bug is unlinked from the test case/test step execution or the test case association with the story is removed afterward, the bug linkage with the Jira story will remain as it is.

The bugs logged while execution is displayed under the Linked Issues section on the Jira Story detail page.