Map Jira Project with QMetry Project

Map Single Jira Project with QMetry Project 

These steps have to be performed in QMetry by Login as QMetry Project Admin: 

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.

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

QMetry allows multiple Jira projects to be configured with one QMetry project. Below are the steps for the same :

1. Go to Projects > Project/Release/Cycle
2. Open the Project > Jira Integration tab.
3. Select the Jira URL with which this QMetry project configuration has to be done.
4. Select the Jira project to configure with QMetry Project.
5. Map Jira Issue Types to QMetry Modules.

Map Jira Issue types to QMetry modules

1. Once the Project is selected, if you are managing your project requirements as Jira stories/epics/sub-task, you should select the Issue Types "Story", "Epic" or "Sub-task" to be associated with the Requirement module. Selection of Issue Type is a multi-select filter, which allows you to select multiple issue types and map with the requirement module. Selection of the folder where the imported issues will be created is mandatory. The first time sync will import all the issues to the selected folder. These issues can later on be moved to other folders in QMetry where any changes done to the issues will be synced. However, all the new stories/epics/sub-tasks that are not part of QMetry will be synced into the selected folder.
2. To map issue types like bugs, tasks or sub-tasks to Issue module, users can select Issue Types associated to Issue module. This is a multi-select filter. The issue types that are mapped with Requirement module can not be mapped with the Issue module and vice-versa. The issues that would be imported and synced with QMetry, would be visible in Issue module with the external key indicating the Jira Issue Key.
3. Click on Save and Activate/update once the configuration is done.  ("Update" if Jira integration was already Saved and Activated for the QMetry project.)
4. Go to Integrations and check the syncing of  Requirement, Issue and Metadata is completed.

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

QMetry allows multiple Jira instances to be configured with one QMetry project. Below are the steps for the same:

1. Go to Projects > Project/Release/Cycle
2. Open the Project > Jira Integration tab.
3. Select the Jira URL with which this QMetry project configuration has to be done.
4. Configure the projects > Save and Activate the Integration.
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 folder to import requirements.
6. Select another Jira URL from the Jira Integration list. 

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.

Map QMetry Folder to Import Requirements

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 requirements while Jira integration.

Users who were using QMetry v8.5 or below, requirements from Jira were imported into 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 -

• Only new requirements will be moved to the synced folder.
• Requirements imported earlier will remain in their assigned folder only.

Copy / Move the Synced Folder

• On Copy/Move Folder, it will move folder to the new folder and update folder mapping on the Project screen as well.

Archive Folder

• Folders with external entities in them can not be archived. Users can move the imported requirements to other folders and then can archive the folder.
• The folder, which was synced during Jira integration for the import of requirements, can not be archived.
• In bulk archive folders, the folders having external entities will be skipped. Subfolders of this folder will also be skipped from the bulk archive even if they do not have external entities.

See also, 

Auto-organize Imported Requirements

Change Mapping of Issue Type with Requirement module

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 longer be Jira issues.

New issues will be synced as requirements as per the changed Issue Type.

Scenario 2. In addition to the existing Issue Type, another Issue Type is mapped with the 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.

Configure System and Custom Jira fields for QMetry Module

QMetry displays default Jira issue fields in QMetry Modules. Project Admin can choose to display Jira system and custom fields as per project requirements. The Configuration of fields has to be done separately for every configured Jira Project and Issue Type.

QMetry provides more flexibility to the administrators in the terms of syncing only the needed fields in QMetry, rather than syncing all the Jira system fields.

• Project admins can now deactivate syncing for specific Jira System Fields within QMetry Requirements and Issues for selected Jira Issue Types. These fields include Description, Component, Fix Version, Priority, Labels, Attachments, Affected Version, Environment, and Assignee.

• Project admins can now sync separate Jira Issue fields for viewing issue details in QMetry and creating issues from QMetry when configuring Jira Issue Types as QMetry Issues.

The following Jira field types are supported in QMetry:

• Number
• Date
• Date and Time
• Single line
• Multiline
• Multi-Look-Up Option
• Single Look-Up Option
• User picker
• Multi-user picker
• Version picker
• Multi-version picker

Note: If QMetry does not display a Jira field on the Configuration screen, sync the project data by clicking "Sync" to configure the field.

Below are the steps : 

1. Configure custom fields for Requirements and Issues.
2. Sync Jira data to QMetry. For example, newly created custom fields, etc.

A. Sync All: It will sync all issues irrespective of their updated date.

B. Sync: It will sync only those issue values that are recently updated in Jira based on their updated date.

Requirement Mapping

While mapping the Jira Issue Type with the QMetry Requirements module, you can make the Jira fields visible or hidden on the Requirements module screen.

Project admins can also deactivate syncing for specific Jira system fields within QMetry Requirements for selected Jira Issue Types. These fields include Description, Component, Fix Version, Priority, Labels, and Attachments.

These fields remain always visible by default and cannot be hidden: Summary, Issue Type, External Key, External Project, Created Date, Updated Date, Resolved Date, and Reporter.

Select the Jira fields (custom/system) you want to map to QMetry and display in requirements. Jira system fields and mandatory custom fields are selected by default. You can keep the fields selected or remove the selection of the fields that you do not want to sync with QMetry. Mapping of Jira fields also affects the listing of fields for hierarchy.

Click Save once you are done selecting or deselecting the Jira fields.

Issue Mapping

While mapping the Jira Issue Type with the QMetry Issue module, you can make the Jira fields visible or hidden on the Issue screen.

• View: If the Jira field is selected under the View column, it will be visible on the list and the detailed view of the issues in QMetry. If the field is not selected, it will not be displayed on the screen.

• Create: If the Jira field is selected under the Create column, it will be visible on the Create screen while creating a new issue in QMetry. You can add values to these fields. If the field is not selected, it will not be displayed on the screen.

  • Note: When the Description field is unchecked, the steps to reproduce the issue will not be auto-populated in the description while creating an issue through the QMetry execution screen.

If both permissions for a field are absent, users cannot view the field details on the test asset's details page. The field columns on the module list view will display "Not mapped for syncing" for these restricted fields.

While mapping the Jira Issue Type with the QMetry Issue module, you can set the “View” and “Create” permissions for the Jira field.

Click Save once you set the required permissions for the Jira field.

Display of Issue fields in Jira and QMetry

In Jira, all Jira fields will be visible irrespective of the permission settings during Jira Field Configuration in QMetry.

In QMetry, the Jira fields will be accessible to the users as per the set configuration.

• View: If the Jira field is selected under the View column, it will be visible on the list and the detailed view of the issues in QMetry. If the field is not selected, it will not be displayed on the screen.

• Create: If the Jira field is selected under the Create column, it will be visible on the Create screen while creating a new issue in QMetry. You can add values to these fields. If the field is not selected, it will not be displayed on the screen.

In cases where both “View” and “Create” permissions for a field are absent, users cannot view the field details on the test asset's details page. The field columns on the module list view will display the "Not mapped for syncing" text for these restricted fields.

Jira’s system and custom fields can be configured (enabled/disabled) for each Jira issue type integrated with the QMetry project.

Note: Jira system fields will be visible in the reports irrespective of the configuration of the Jira system field in QMetry. It means the Jira system fields will still be visible in the reports even if that system field is not selected in the issue type configuration.

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 Projects should be integrated with the 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 the Integration Scheduler Status tab under Integration > Integrations.

View Jira Integration Status

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 update on the integration status of Jira and QMetry projects.

Steps

1. Expand Integration on the sidebar menu and select Jira Integrations. There are two tabs on the screen: Integration and Jira Scheduler Status.
2. Open the Integration tab.