/
Projects using Jira integration for Issue (Bug) Tracking

Projects using Jira integration for Issue (Bug) Tracking

This document is applicable only when the QMetry project is configured with a Jira project.

The Issue module enables internal issue management within QMetry. Users can create, view, and modify issues without external tool integration. Custom fields can be added to tailor issue details to business needs.

The Issue module allows users to have bi-directional integration between QMetry and Jira, meaning users can add and edit issues from QMetry to Jira. Issues added or edited in Jira will be reflected in QMetry. Users can create, view, and modify issues in QMetry, and these changes will be synced with Jira.

Users can perform the following tasks in the Issue module:

  • View/ Add/ Modify Jira issue details, comments and attachments

  • Map Jira custom fields with QMetry

  • Issues logged from the execution screen while execution will be available in the Issue module.

After integrating QMetry project with Jira -

  • QMetry issues added from the Issues module before Jira integration will not be displayed on the Issue grid.

  • QMetry issues created and linked from the Execution screen before Jira integration will be displayed in read-only mode.

  • From the Execution screen, clicking on an internal issue link opens its details in read-only mode.

View, Add, Modify issues

View and Organize Issue Details

To view an issue detail page:

  • Same Page: Click the Issue Key in the grid view.

  • New Tab/Window: Right-click the Issue Key and select "Open in New Tab" or "Open in New Window."

Opening issues in a new tab or window facilitates easier comparison and provides quick reference while managing multiple assets. The detail page features organized tabs for easy navigation to different sections.

Note:

  • If a Jira project is integrated with QMetry project -

    • Bulk operations are not allowed in the Issue module.

    • Column show/hide 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, Comments.

1. 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 QMetry. 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 QMetry.

  • Resolution: A read-only field synced from Jira.

  • Environment: Enter details of the environment where the issue was found (e.g., 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.

Watcher, Owner and Assigned Release are not available for projects integrated with Jira.

2. Execution Runs

Issues logged from the Test Executions module are displayed here.

View Archived Test Runs

An execution/test run is archived when either Platform/Release/Cycle/Test Suite is archived. When a test suite, platform or Release/Cycle is archived, the test executions having such test suite/platform/release/cycles 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 a test execution, open the issue detail page and navigate to the Execution Runs tab.

Two columns Execution Time and Remaining Time are added on the grid at the following places in the application:

  • Test Suite detail page > Test Executions tab

  • Test Case detail page > Test Executions tab

  • Issue detail page > Execution Runs

Calculation of Execution Time of a test suite: Execution Time of a test suite is calculated based on Estimate Time of all the test cases in that test suite.

Calculation of Remaining Time of a test suite: Once the test suite is executed, the Remaining Time Is calculated of all “Not Run” test cases. Any test case with “Failed” or “Blocked” status will also be considered as the work still remains on it. The Remaining Time will be reduced for test cases with “Pass” and “Not Applicable” status accordingly.

Example

The example below illustrates the calculation of both Execution Time and Remaining Time.

 

Execution time

Status

Remaining time

 

Execution time

Status

Remaining time