...

Just click on the Issue Key in the grid view to open the issue detail page on the same page. To open the issue detail page in a new tab/window,  right click on the Issue Key in grid view. Opening issues in different tab/browser makes a comparison between issues easier. It also provides quick reference while working on multiple assets. The detail page has one click access to different sections using organizable tabs.

...

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

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

5. Fill in the issue details.

• Summary: View the summary of the Issue.

• Priority: View priority to the issue. The Priority list will be displayed as in Azure.

• Work Item Type: View the issue type synced with the Issue module while integration.

• Tags: View list of Azure tags in QMetry.

• Stack Rank: View list of Azure in QMetry.

• Effort: View list of Azure in QMetry.

• Assigned To: This will be the Azure Assignee.

• Area Path: Browse the folder in Azure and select the path.

• Iteration Path: Browse the folder in Azure and select the path.

• State: View Azure workflow Status of issue in QMetry. This is a Read-only field.

• Created By: Azure user who has reported the issue.

• Team Project: This is a read-only field synced from Azure.

• Description: Enter description for the issue in plaint text.

• Azure Custom Fields: View Azure custom fields, if any.

...

Edit Issues

QMetry provides an inline editor to edit issue details.

...

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

Users can log issues at the test case as well as test step level. Users can also log issues in bulk.

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

Delete Issue

...

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 the 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 Azure issues from QMetry. If an issue is deleted from Azure, then it will get deleted from QMetry and its linkages to the QMetry test case/test step will be removed as well.

When Azure Configuration is Removed

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

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

• Issues created in QMetry internal tracker before Azure 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 a filter on. The filter parameter is added as Advanced Filters. Apply filter as per your requirement.

Users 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).

...