...

Execution Runs

Issues logged from the Test Executions module are displayed here.

...

Requirements can be linked to the issue through the Requirements tab of Issue.

...

You can select requirements on the grid to link to the issue. You 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.

...

If you want to link requirements from multiple projects, then first select one project. Search records and link them before moving to other projects. For example, User A is in Project 1 and searches for some records and link links them before moving to Project 2. Else, all the selection of Project 1 will be wiped off.

...

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

...

If requirements from other project are linked, then the requirements show the Entity Key of the corresponding project.

...

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

...

The fields are shown as mandatory/optional as per their project configuration in Jira.

...

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

Users can click on the External Key in the Issue module, which opens the issue detail page in Jira, while the Entity Key opens the issue detail page in QMetry.

The issue details to enter depends on whether you are adding issues in the internal tracker of QMetry or in Jira.

• If you do not have Jira configured with the project you are currently working on, then enter details in the QMetry fields.

• If you have configured Jira with the project you are currently working on, then the add issue screen contains Jira issue fields that you need to enter. You can add defects from the Issue module as well as the Execution screen of QMetry.

6. Fill in the issue details.

• Summary: Add the summary of the Issue.

• Priority: Select priority to the issue. The Priority list will be displayed as in Jira.

• Issue Type: Select the issue type synced with the Issue module while integration.

• Assignee: This will be the Jira Assignee. Enter the first three letters of Jira user to populate the Jira users list.

• Status: This field will not be available when you are creating an issue. Default Jira issue status will be auto-selected when the issue is created.

• Reporter: Jira user who has reported the issue. Enter the first three letters of Jira user to populate the Jira users list.

• Components: Select Jira components associated to the project.

• Fix Versions: Select Jira Fix Versions associated to the project usually added when the issue is resolved.

• Affects Versions: Select Affects Versions associated to the project usually this is applicable only for bugs and not for stories or epics. It denotes in which version the bug was found.

• Labels: Select list of Jira labels in QMetry.

• Environment: Enter environment details in which the issue was found e.g., Chrome, Firefox, Production, Staging, etc.

• Description: Enter a description for of the issue in plaint text. You can use the text formatting notations in the field as per Jira Wiki Editor.

• Jira Custom Fields: Enter Jira custom fields like Sprint, Severity, etc.

...

Open the Execution screen and click on the bug icon for test case/test step. Refer to Adding/Linking Issues to Test Case and Test Step for more details.

Creating Issues at Step Level for Automated Test Cases

If an error encounters while an automated test run, the generated Error Message and Trace are displayed in the respective columns on the test execution screen. When users create an issue at test step level from the execution screen, a .txt file containing this Error Message and Trace got 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 can not delete Jira issues from QMetry. If  If an issue is deleted from Jira , then it will get deleted from QMetry and its linkages to QMetry test case/test step will be removed as well.

When Jira Configuration is Removed

• On removing the integration of Jira project with QMetry project, all the issues that are created from QMetry Issue module into Jira will not be visible in the Issue module in QMetry.

• For Jira issues logged while execution, the association of such Jira issues with respective test case/test step will be removed.

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

Manage Issue View

The following columns are displayed on the list view:

...

Select the field you want to apply filter on. The filter parameter is added as Advanced Filters. Apply filter as per your requirement.

User can click on the '+' icon and select the field Entity Key to search issues using comma separated entity IDs (i.e without specifying the complete Entity Key as described below).

...