Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Go to Projects > Project/Release/Cycle
  2. Open the Project > Jira Integration tab.
  3. Select the Jira URL with which this QMetry project mapping has to be done.
  4. Select the Jira project to configure with this QMetry Project.
  5. Once the Project is selected, select Issue Type <> QMetry Module associations. The issue type is a multi-select list. If the requirement is mapped, select the folder to import requirements.
  6. Click on Save and Activate.



1. Jira sub-tasks issue types are not supported in the Requirement or Issue module.

2. If Epics are can be imported as requirements in QMetry -

  • "Epics" are supported with limited fields. Fields like Epic Color, Epic Links, etc. are not supported. Epics are imported into QMetry as individual requirements. Any association of Epic with the stories is not preserved in QMetry. If Story and Epic both Issue types are synced with Requirement, the  Epic imported as a requirement will display the Epic Name on the requirement details page while the Story imported as a requirement will display the Epic Name field blank.

3. If Epic is imported as issues in QMetry -

If Epic is synced with Issue, the Epic issues will be available while logging bugs. Only "Epic Name" in Jira Fields is available for the "Epic" type during the creation of an issue from the execution screen

as Requirements or Issues. The Epic fields - Epic Link, Epic Status, Epic Color and Epic Name are supported and are available in the Jira details section of an Epic imported as a Requirement or Issue. Issues that are part of these Epics can be viewed in the "Issues in Epic" tab.

To view the issues of the Epic under the "Issues in Epic" tab, their issue types must also be integrated with the Jira project and synced in QMetry. These issues show the "Epic Link" (Epic Key) to trace back to its Epic.

Map multiple Jira projects from multiple Jira instance with one QMetry project


If the user changes already set folder, then a pop-up appears asking confirmation on changing changing the destination folder for new requirements that are being imported. The impact will be -