Overview

Once you configure and map the Jira issue types, the system automatically imports the requirements into the selected folder. All fields from Jira are synced to QMetry, and Jira fields displayed as read-only.

QMetry auto-syncs all Jira fields during the initial setup. To reflect newly added custom fields in Jira, you can manually sync the projects. By default, imported requirements are added to the “Import” folder specified during mapping.

Pre-requisites

• Configure the Jira project with a QMetry project.

• Map relevant Jira issue types to the Requirement module.

Syncing Requirements from Jira

QMetry auto-syncs all Jira fields during the initial setup.

To reflect newly added custom fields:

1. Navigate to Jira Integrations.

2. Click Sync Projects.

Managing the Import Folder

Move Synced Requirements to Another Folder

You can move Jira-synced requirements from the default “Import” folder to another folder. Synced requirements when moved are not re-imported to the default folder. They continue to sync in the new folders.

Archiving Folders Containing Synced Requirements

Folders containing Jira-synced requirements (including archived requirements) cannot be archived or deleted directly. To archive or delete such folders, you must move all requirements to a different folder.

To Archive folder having archived requirements, perform the following steps:

1. Unarchive the requirements.

2. Bulk move the requirements to another folder.

3. (Optional) Re-archive the requirements.

4. Archive or delete the now-empty folder.

Viewing Requirement Details in QMetry

Jira synced requirements display the following information:

1. Jira System and Custom Fields (including Sprint and Labels).

2. Latest 10 Comments and Attachments from Jira issue.

The QMetry panel on the Jira issue page displays test case linkages to the requirement.
It also shows the QMetry Project linked to the Jira story. Once you select the project, the QMetry Key is populated for the issue synced as a requirement in QMetry.

Test Case Execution in Jira

The Test Case section on the story page displays linked test cases and their execution details. This helps developers and product managers track test execution summary directly on the Jira story page.

Use the Filter icon in the Test Case section to filter executions by Release, Cycle, Platform, Build, or Test Suite Key.

View Test Case Execution Summary

Click the graph icon to view execution statistics.

1. Select latest execution or all executions.

2. Click to view summary of statuses. All custom statuses gets displayed.

3. Count of issues linked to test cases and steps during the execution.

Sync Issues from Jira to QMetry

Once Jira issue type is mapped to the Issue module in QMetry, you can:

• Create new issues in Jira directly from QMetry while executing test cases.

• Link existing Jira issues to test cases or individual test steps.

• View issues that are already linked.

QMetry Issue module remains visible even if the QMetry Project is integrated with Jira Project.

Refer to Projects using Jira integration for Issue (Bug) Tracking for more details.

Create Jira issues from the Test suite execution window

Test case and Step details are automatically added to the Issue Description.

Link Jira Issues from the Test Suite Execution Window

To link Jira Issues from the Test suite execution window, perform the following steps:

1. Navigate to the Available Issues tab.

2. Select the issues.

3. Click Link and Close.

The linked issues appear under the Linked Issues tab.

Sync Deletion of Requirements or Issues in Jira

When a requirement or issue is deleted in Jira, QMetry automatically deletes the corresponding item.

Linking Issue to Requirement in QMetry

For projects integrated with Jira, if bugs are directly linked to requirements in QMetry, they appear as issue links on the corresponding Jira story page.

The following image displays Bugs directly linked to Requirements in QMetry.

If the requirement is associated with test cases, then issues linked to the test cases (either directly or indirectly through execution) will also appear on the Issues tab of that requirement.

• The linked issue gets displayed in the corresponding story/issue in Jira under the Linked Issues section if the story and issue linked in QMetry are from the same Jira instance.

• If the issue is unlinked in requirement in QMetry, the issue in Jira also gets unlinked from the corresponding story/issue in Jira. The linkage relation will not be displayed in Jira anymore.

• If an Issue link is deleted from Jira Story for an Issue Linked to QMetry Requirement, it does unlink the bug in QMetry Requirement.

• If an Issue link is added in a Jira Story in Jira for a Requirement Imported in QMetry. The issues will not be auto-linked in QMetry.

• The story in Jira reflects linked issues under the Linked Issues section as “relates to”.

Clicking on the issue key in the Issue links opens the issue details page in Jira.

• The QMetry Test Case panel will show the details of the Test Case and the Test Execution on which this bug is logged.

• Test Case will have two tabs: Test Case Steps and Executions.

The Test Case Steps tab shows steps under the test case.

The Executions tab shows the execution during which the issue was logged.

If the issue is directly linked to the test case without its execution, then the Executions tab will not show any execution details.