Projects using Jira integration for Issue Tracking
Note
This document applies only when a project is configured with an Azure project.
The Issue module provides bi-directional integration between and JIRA. You can create, view, and edit issues in , and the changes sync to JIRA. Likewise, issues added or updated in JIRA appear in .
You can perform the following tasks in the Issue module:
View, Add or Modify Jira issue details, comments, and attachments.
Map Jira custom fields with .
Access issues logged during test execution in the Issues module.
After integrating the QMetry project with Jira -
The system do not display issues added from Issues module before integration in the Issue grid.
Issues created and linked from Execution screen before Jira integration are displayed in read-only mode.
Clicking an internal issue linked from the Execution screen opens the detail window in read-only mode.
Viewing and Organizing Issues
Click the Issue Entity Key in the grid view to open the issue detail page.
You can customize the grid view by resizing columns, organizing tabs, or applying filters and sorting. To learn more, refer to Manage Grid Columns.
Note
If a Jira project is integrated with a project:
Bulk operations gets disabled in the Issue module.
Column show or hide option is not available in the Issue module, however; you can filter the records including Jira system and custom fields.
 |
In the issue module, there are individual tabs for - Details, Execution Runs, Requirements, Attachments, and Comments.
Details tab
The Details tab displays issue information from Jira:
External Key: Click this Jira issue key to navigate to the Jira issue page.
Summary: View the issue summary.
Priority: Displays the issue priority as per Jira.
Issue Type: Shows the issue type synced from the Issue module during integration.
Assignee: Displays the Jira assignee.
Status: Shows the Jira workflow status of the issue in . This is a read-only field.
Reporter: Indicates the Jira user who reported the issue.
Components: Displays Jira components associated with the project.
Fix Versions: Shows Jira fix versions related to the project, typically added when the issue is resolved.
Affects Versions: Lists affected versions, usually applicable to bugs, indicating where the bug was found.
Labels Displays Jira labels in .
Resolution: A read-only field synced from Jira.
Environment: Enter details of the environment where the issue was found (Chrome, Firefox, Production, Staging).
Description: Enter the issue description in plain text.
Jira Custom Fields: View Jira custom fields such as Sprint and Severity.
Created Date: The date the issue was created in Jira.
Updated Date: The date the issue was last updated in Jira.
Resolved Date: The date the issue was marked as resolved in Jira.
Note
Watcher, Owner, and Assigned Release are not available for projects integrated with Jira.
Execution Runs
Issues logged from the Test Executions module are displayed here.
View Archived Test Runs
Execution runs are archived when the associated Platform, Release, Cycle, or Test Suite is archived. When a test suite, platform or Release/Cycle is archived, the test executions associated with them will be hidden on the Execution Runs tab of the test case.
To view archived test runs, select the Show Test Runs with Archived Platform(s)/Release(s)/Cycle(s)/Test Suite(s) checkbox on the Test Executions tab.
Execution Time and Remaining Time
To view Execution Time and Remaining Time for test execution, open the issue detail page and go to the Execution Runs tab.
The columns Execution Time and Remaining Time are added to the grid in the following locations within the application:
In Test Executions tab under Test Suite detail page.
In Test Executions tab under Test Case detail page.
In Execution Runs tab under Issue detail page.
Execution Time of a Test Suite: Calculated based on the estimated time of all test cases within the suite.
Remaining Time of a Test Suite: Calculated for all "Not Run" test cases after execution. Test cases marked as "Failed" or "Blocked" are also considered as having remaining work. The Remaining Time is adjusted for test cases with "Pass" and "Not Applicable" statuses.“Not Applicable” status accordingly.
Execution time | Status | Remaining time | |
|---|---|---|---|
TC1 | 2 | Pass | - |
TC2 | 3 | Not Applicable | - |
TC3 | 4 | Failed | 4 |
TC4 | 5 | Blocked | 5 |
14 | 9 |
Linking Requirements to Issues
Link single or multiple requirements to an issue through the Requirements tab on the Issue details page.
To link requirements to issues, perform the following steps.
Open the Issue details page.
Go to the Requirements tab.
Click the Link icon to attach an individual requirement or select the requirements and click Link or Link & Close.
Select the requirements. Use filters, including Labels and Folder Paths, to narrow down the list.
Click Link & Close.
Project Selection for Cross Project Association
 |
You can link requirements from multiple projects. Select the project containing the requirements to link.
To link requirements across projects, select a project, link its records, then switch to the next project. Remember, switching projects clears previous selections, so click Link before moving on.
Viewing Linked Requirements
The system links the selected requirements to the issue, and the linked records are displayed on the screen.
The linked requirements are displayed on the screen. If a requirement belongs to another project, its Entity Key is shown. Clicking the Entity Key opens the requirement in that project and switches you from the current project.
Unlink Requirements
Go to the Requirements tab of the issue.
Go to the Requirements tab of the issue.
To unlink a single requirement, click the Unlink icon for the requirement. The requirement is unlinked after confirmation.
To unlink multiple requirements, select the requirements you want to unlink from the issue and click on the Unlink Selected
Attachments
You can view, download, add, and delete Jira attachments in . Refer to Managing Attachments to know more.
Comments
You can view, add, edit, and delete Jira comments in . Refer to Add Comments to know more.
Logging issues from Issue Module to Jira
To log issues from an issue module, perform the following steps:
Open the Issue module.
Click New.
Note
Logging an issue for the First Time
Authenticate using Jira Username and Password (if Server Jira) or API Token (if Cloud Jira) to authenticate and modify the Jira entity.
Username: Enter Username.
API Token: Follow the steps mentioned in the article Login using API Token to generate API Token.
Select Jira Instance, Jira Project and Issue Types. The system displays the fields as per the selected Issue Type. The fields are shown as mandatory or optional as per their project configuration in Jira.
Issues added from the Issue module or Execution screen are created in Jira.
External Key: Opens the issue detail page in Jira.
Entity Key: View the issue detail page in .
Enter issue details:
Without Jira Configuration: Enter details in fields.
With Jira Configuration: The add issue screen will display Jira fields to complete.
Defects can be added from both the Issue module and Execution screen in .
Fill in the issue details as follows:
Summary: Add the issue summary.
Priority: Select the priority from the Jira list.
Issue Type: Choose the issue type synced with the Issue module.
Assignee: Enter the first three letters of the Jira user to populate the list.
Status: This field is not available during issue creation. The default Jira status will be auto-selected.
Reporter: Enter the first three letters of the Jira user to populate the list.
Components: Select the Jira components for the project.
Fix Versions: Select the Jira fix versions, usually added when the issue is resolved.
Affects Versions: Choose the affected versions, typically for bugs, to indicate where the bug was found.
Labels : Select Jira labels available in
Environment: Enter the environment where the issue was found (e.g., Chrome, Firefox, Production).
Description: Describe the issue using Jira Wiki Editor formatting if needed.
Jira Custom Fields: Enter Jira custom fields such as Sprint and Severity.
Link Attachments: Attach files during issue creation.
Status
After adding the issue, the following tabs appear: Details, Execution Runs, Requirements, Attachments, and Comments.
Editing Issues Details
Once the issues are added, open the Issue details page to view or edit the details. Use an inline editor to edit issue details.
Note
Jira issue Status, Issue Type and Resolution are read-only fields in and can not be edited.
Logging Issues from the Execution Screen of the Test Suites Module
Log issues at both the test case and test step levels, including in bulk.
Open the Execution screen.
Click the bug icon next to the test case or test step to log an issue. For more details, refer to Adding or Linking Issues to Test Case and Test Step
Creating Issues at the Step Level for Automated Test Cases
During an automated test run, if an error occurs, the system shows an Error Message and Trace on the test execution screen. When users create an issue at the test step level, the system automatically attaches a .txt file with the Error Message and Trace to the issue.
On opening the issue in , the Attachment tab shows the .txt file attached to it which contains the Error Message and Trace.
Map Jira custom fields with
System fields are automatically mapped and displayed as read-only. Users can select custom fields to map, which will then appear in the Issue module.
To make the Reporter field mandatory, turn on the flag.
 |
Create Requirement from Issue
To create a requirement from an issue:
Select the issue and add a new requirement.
The new requirement will copy common field values from the issue and use the same name, which can be edited.
The issue will be automatically linked to the new requirement. On the Issue details page, the Requirements tab will show this new requirement. On the Requirement details page, the Issues section will show the originating issue. Only users with “Create” rights for Requirements can perform this action.
Steps:
From the Toolbar: Select an issue in the grid pane, click "Add" on the toolbar, point to "From Issue," and select "Requirement."
From Context Menu: Right-click an issue in the grid pane, point to "From Issue," and select "Requirement."
Delete Issue
You cannot delete Jira issues from . If an issue is deleted in Jira, it is removed from , and its linkages to test cases or test steps are deleted.
When Jira Configuration is Removed
When Jira project integration is removed from a project:
Issues created in Jira from the Issue module is longer be visible in .
Jira issues logged during execution will lose their association with test cases or test steps in .
Issues created in the internal tracker before Jira integration will reappear in the issue grid.
Edit or Revoke Existing Jira Authentication
When adding an issue for the first time, the Jira Authentication window will prompt for credentials. This window will not appear again for subsequent operations.
To display the Jira Authentication window again, revoke the existing credentials:
 |
Go to Jira Integrations.
Click the cog icon and select Revoke credentials.
Email Issue Details to Other Users
You can share defect or issue details with others, including those outside . Details include system fields, and attachments depending on the issue tracker.
If an External Tracker is integrated with Jira, details are sent in a predefined format without attachments.
To email issue details, perform the following steps:
Open the issue details page to share.
Click the email icon at the top right.
Enter recipient email addresses, separated by commas, and send the email.