Sync Requirements & Issues

QMetry panel in Jira now has separate sections for synced requirements, linked test cases and BDD details.

Sync Requirements from Jira to QMetry

Once Jira Project is configured with QMetry Project and Mapping of issue type with QMetry Requirement module is done. Requirements will be imported in the Requirement module as per the selected folder while Jira integration. Syncing of Jira fields is unidirectional i.e from Jira to QMetry. Once the requirements are imported only the QMetry fields can be edited, the Jira fields will be Read Only. 



Requirements get imported into a default “Import” folder (i.e. setup while integrating Jira Project issue types) in QMetry.

Things to know:

  1. Jira Synced Requirements, imported to the above set default “Import” folder, can be moved to other folders.

  2. Synced Requirements that are moved, do not get re-imported to the default “Import” folder again, and they continue to sync in the folders where they are moved.

  3. You can not archive (and subsequently delete) a default set “Import” folder in which requirements get imported from Jira.

  4. You can not archive any folder that contains Jira Synced Requirements (including archived requirements).

    • To archive (and then delete) such folders, all requirements that exist in the folder must be moved to a different folder.

    • To Archive folder having archived requirements

a. First un-archive the requirements.

b. Bulk Move the requirements to other folders.

c. Archive the now un-archived requirements again, if required.

d. Now the empty folder can be archived/deleted.

Requirement detail screen displays below information of Jira issues :

  1. Jira Fields - System and Custom Fields. Jira fields Sprint and Labels fields are also synced in QMetry.

  2. Latest 10 Comments & Attachments from Jira issue.


Test case linkages to Requirement are shown in Jira on the issue page under the QMetry panel.

QMetry Project: It displays QMetry Projects with which the Jira story is synced. If the story is synced in more than one QMetry project, the drop-down will show more than one QMetry Project.

Once you select the project, QMetry Key populates for the issue synced in QMetry as a requirement.

Jira New View: Clicking on the QMetry button navigates you to the QMetry panel.

Jira Old View:

Sync Issues (Defects/Bugs) from Jira to QMetry

Once Jira Project is configured with QMetry Project and Mapping of issue type with QMetry Issue module is done. Users can create a new issue from QMetry to Jira while executing test cases, link existing issues of Jira and view already linked issues. The issue can be linked to Test Cases or Test Case steps.

QMetry Issue module will still be 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.

Jira New View:

Jira Old View:


The Test Case section in Jira will show the details of the test case.



View already linked/newly created issues on the Test suite execution window.

Sync Deletion of Requirements/Issues in Jira

QMetry is more synced with Jira. When a requirement/issue is deleted in Jira, the same requirement/issue also gets deleted in QMetry.

Linking Issue to Requirement in QMetry

For QMetry projects integrated with Jira, having Jira Stories and Bugs synced in QMetry as Requirements and Issues - when Bugs are directly linked to Requirements in QMetry, those Bugs will appear as Issue Links in Jira Story Page.


The Issue Links in Jira are created only when the user has authenticated with their Jira credentials in QMetry. Issue links are generated in Jira by a cron job that runs every 5 minutes.

  • To authenticate users need to go to QMetry > Integrations > Integrations.

  • Go to Integrations tab > Click on Options cog icon > Configure. Enter the Jira Credentials.

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

  • 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.