Introduction

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.

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 the 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.

2. 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. Archived test runs will be hidden on the Execution Runs tab if they are linked to these archived entities.

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 based on 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 = 14

Remaining Time = 9

Requirements tab

Link Requirements to Issue

Users can link single or multiple requirements to an issue through the Requirements tab on the Issue details page.

Steps

1. Open the Issue details page.

2. Go to the Requirements tab.

3. Click the Link button.

4. On the Link Requirement screen, select requirements from the grid to link to the issue.

5. Use filters such as Labels and Folder path to refine the list (if needed).

Users can select requirements on the grid to link to the issue. They can filter requirement records to narrow down the list to select from. Labels and Folder path filters are also added for the ease of searching the records.

Link Requirements Across Projects:

Users can link requirements from different projects by selecting the project from the Project drop-down menu. Requirements for the selected project will be displayed.

To link requirements from multiple projects, users should:

1. Select a project.

2. Search for and link the required records.

3. Move to the next project.

For example, User A should complete linking records in Project 1 before switching to Project 2. Otherwise, selections from Project 1 will be lost.

A. Linking a Single Requirement: Click on the 

​ icon to link the individual requirement to the test case.

B. Linking Multiple Requirements: Select requirements that you want to link and click either on the Link button or Link & Close button at the bottom.

View Linked Requirements

The selected requirements are linked to the issue, and the linked records are displayed on the screen.

For requirements from other projects, the Entity Key of the respective project is shown. Clicking on the Requirement Entity Key opens the detail page in the relevant project and changes the current project view.

Unlink Requirements

Navigate to the Requirements tab of the issue.

A. To unlink a single requirement, click on the Unlink icon for the requirement. The requirement is unlinked after confirmation.

B. To unlink multiple requirements, select requirements to unlink from the issue and click on the Unlink Selected button.

Attachments

Refer to Managing Attachments for details.

Comments

Users can view, add, edit, and delete Jira comments in QMetry.

Add Issues / Bugs / Defects

A. Steps to log issues from Issue Module to Jira

1. Open the Issue module.

2. Click on the New button on the toolbar.

Logging an issue for the First Time

Users are requested for Jira authentication through the pop-up.

• Username: Enter Username.

• API Token: Follow the steps mentioned in the article Login using API Token to generate API Token.

To Edit/Revoke Authentication

If Jira credentials are changed, then follow Revoke Authentication to modify the credentials in QMetry.

4. The Create Issues screen opens next.

5. Select Jira Instance and Jira Project.

Issues added from the Issue module or Execution screen will be created in Jira.

• External Key: Click to open the issue detail page in Jira.

• Entity Key: Click to view the issue detail page in QMetry.

Enter issue details based on whether Jira is configured with the current project:

• Without Jira Configuration: Enter details in QMetry 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 QMetry.

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

• Environment: Enter the environment where the issue was found (e.g., Chrome, Firefox, Production).

• Description: Provide a description of the issue using Jira Wiki Editor formatting if needed.

• Jira Custom Fields: Enter Jira custom fields such as Sprint and Severity.

• Link Attachments: To add attachments:

  1. Go to the Link Attachments section on the Create Issue page.

  2. Click the Add Attachment button.

Users can attach files, images, and URLs using the Add Attachment pop-up, which supports multiple uploads at once.

Attachments can be added in three ways:

• Drag and Drop: Drag files into the designated area.

• Browse: Click the Browse section to select and upload files.

• Paste (Ctrl + V): Paste screenshots directly from the clipboard. Only .png files can be pasted.

Users can also remove individual attachments at the uploading stage.

Edit Issues

QMetry provides inline editor to edit issue details.

B. Steps to log issue from Execution screen of Test Suites Module

Users can log issues at both the test case and test step levels, including in bulk.

To log an issue:

1. Open the Execution screen.

2. Click the bug icon next to the test case or test step.

For more details, refer to Adding/Linking Issues to Test Case and Test Step.

Creating Issues at Step Level for Automated Test Cases

If an error occurs during an automated test run, the Error Message and Trace are displayed in their respective columns on the test execution screen. When users create an issue at the test step level, a .txt file with the Error Message and Trace is automatically attached to the issue.

On opening the issue in QMetry, the Attachment tab in QMetry shows the .txt file attached to it which contains Error Message and Trace generated while the automated test run.

Delete Issue

• Users cannot delete Jira issues from QMetry. If an issue is deleted in Jira, it will also be removed from QMetry, and its linkages to QMetry test cases or test steps will be deleted.

When Jira Configuration is Removed

• When Jira project integration is removed from a QMetry project:

  • Issues created in Jira from the QMetry Issue module will no longer be visible in QMetry.

  • Jira issues logged during execution will lose their association with test cases or test steps in QMetry.

  • Issues created in the QMetry internal tracker before Jira integration will reappear in the issue grid.

Manage Issue View

Users can customize their view -

• Resize Columns: Users can adjust the width of the columns.

• Organize Tabs - The detail page of QMetry assets includes various tabs, which users can customize by changing their order. This tab order is saved for each user.

Filter Issues: Users can easily filter test assets by any system/custom field on all module grids.

Apply Filter

Users can apply basic as well as advanced filters to the records.

Select the field to apply filter on. The filter parameter is added as Advanced Filters. Apply filter as needed.

Clear Filter and Sorting

Users can clear the applied filter and sorting to the records.

A. Clear Filter: Click on the Clear Filters button above the module grid or left pane. It will reset the view to default.

B. Clear Sorting: Click on the Clear Sorting button above the module grid.

Map Jira custom fields with QMetry

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.

Log Issues/Bugs/Defects from Execution Screen

Issues logged from the execution screen while execution will be available in the Issue module. Refer to Adding/Linking Issues to Test Case and Test Step for more details.

Create Requirement from Issue

To create a requirement from an issue:

1. Select the issue and add a new requirement.

2. 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:

1. From the Toolbar: Select an issue in the grid pane, click "Add" on the toolbar, point to "From Issue," and select "Requirement."

2. From Context Menu: Right-click an issue in the grid pane, point to "From Issue," and select "Requirement."

Edit/Revoke Existing Jira Authentication

Anchor

Anchor

​

If 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:

1. Go to Integration > Jira Integrations.

2. Click the cog icon and select Revoke credentials.

Status:

Once the Issue is added, the following tabs appears - Details, Execution Runs, Requirements, Attachments, Comments

Edit Issue Details

Once the issues are added, open the Issue details page to view / edit the details.

Email Issue Details to Other Users

Users can share defect or issue details with others, including those outside QMetry. Details include QMetry system fields, and attachments depend on the issue tracker.

• External Tracker: If integrated with Jira, details are sent in a predefined format without attachments.

Steps:

1. Open the issue details page to share.

2. Click the email icon at the top right.

3. Enter recipient email addresses, separated by commas, and send the email.