These steps have to be performed in QMetry by Login as QMetry Project Admin :
QMetry allows multiple Jira projects to be configured with one QMetry project. Below are the steps for the same :
Map Jira Issue types to QMetry modules
1. Jira sub-tasks issue types are not supported in the Requirement or Issue module. 2. Epics can be imported in QMetry 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. Read about Epic Traceability. |
QMetry allows multiple Jira instances to be configured with one QMetry project. Below are the steps for the same:
7. Configure the projects > Save and Activate the integration.
8. 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 a folder to import requirements.
This way you can integrate multiple Jira instances with QMetry Project.
Project Admin has to select a folder during Jira configuration to import requirements from Jira into QMetry. QMetry v8.5.1 onwards, it is mandatory to select a folder for requirement while Jira integration.
Users who were using QMetry v8.5 or below, requirements from Jira were imported in the Imported folder in QMetry by default. QMetry v8.5.1 onwards, Project Admin has to select a folder of their preference to import requirements in QMetry. Requirements already imported earlier will remain intact in their respective folders. New requirements will be imported in the folder selected during Jira configuration.
If the user changes already set folder, then a pop-up appears asking confirmation on changing the destination folder for new requirements that are being imported. The impact will be -
Copy / Move the Synced Folder
Archive Folder
Scenario 1. Issue Type mapped with Requirement is replaced with another Issue Type
Issues synced based on the earlier mapping will be converted into internal issues and they will no more be Jira issues.
New issues will be synced as requirements as per the changed Issue Type.
Scenario 2. In addition to existing Issue Type, another Issue Type is mapped with Requirement
Issues synced based on the earlier mapping will remain intact as Jira issues.
New issues will be synced as requirements as per the added Issue Type.
QMetry displays default Jira issue fields in QMetry Modules. Project Admin can choose to display Jira custom fields as per project needs. Configuration of custom fields has to done separately for every configured Jira Project and Issue Type.
The following Jira field types are supported in QMetry:
Below are the steps :
Note : In case QMetry does not display a Jira field in the configuration screen - "Sync" project data to configure the field.
A. Sync All: It will sync all issues irrespective of their updated-date.
B. Sync: It will sync only those issue values which are recently updated in Jira based on their updated-date.
Jira’s custom fields can be configured (enabled/disabled) for each individual Jira issue types integrated with the QMetry project.
You can sync the mapped Jira custom fields in the QMetry Insight module for Visual Reports and Advanced Query Reports. Read more about Sync fields to Reports.
Note : At least one of the Jira Project should be integrated with Issue Module. Once the Jira is integrated with the QMetry project the internal issue module will be disappeared from the QMetry project.
You can view the status under Integration Scheduler Status tab under Integration > Integrations.
Users can view all the integrated Jira instances, their associated QMetry projects, and their current Status either Active or Inactive.
The Integration tab gives you a quick idea of the status of Jira and QMetry project integration.
Steps