Back to QMetry All Products Help Page
Projects using Azure integration for Issue (Bug) Tracking
This document is applicable only when the QMetry project is configured with a Azure project.
Issue module allows you to have bi-directional integration between QMetry and Azure, which means you can add and edit issues from QMetry to Azure. Issues added / edited in Azure will be reflected in QMetry. Users can create, view, and modify issues in the QMetry that will be synced in Azure.
Users can perform the following tasks in the Issue module:
View/ Add/ Modify Azure issue details, comments and attachments
Map Azure custom fields with QMetry
Issues logged from the execution screen while execution will be available in the Issue module.
After integrating QMetry project with Azure -
QMetry issues added from the Issues module before Azure integration will not be displayed on the Issue grid.
QMetry issues created and linked from Execution screen before Azure integration will be displayed in read-only mode.
If users click on the link of an internal issue which is linked from the execution screen, its detail window open in read-only mode.
View, Add, Modify issues
View and Organize Issue Details
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 new tab/window, right click on the Issue Key in grid view. Opening issues in different tab/browser makes 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.
For Issue: There are individual tabs for
Details
Execution Runs
Requirements
Attachments
Comments
Details tab
The Details tab will show you the issues details in Azure.
External Key: This is the Azure issue key number clicking on which takes users to the Azure issue page.
Title: 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.
Note: Watcher, Owner and Assigned Release are not available for projects integrated with Azure.
Execution Runs
Issues logged from Test Executions module are displayed here.
Execution Time and Remaining Time
Open the issue detail page and open the Execution Runs tab. Users can view Execution Time and Remaining Time calculated for Test Execution.
Use Case: Calculation of Execution Time and Remaining Time for test suite is useful for QA Manager in Test Planning as it gives accurate estimates for the test suite. These test case level estimates refine each time a test suite is executed. Testers can make recommendations to have the test estimates revised based on the last few executions in different environments.
Two columns Execution Time and Remaining Time are displayed 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 tab
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.
Requirements tab
Link Requirements to Issue
You can link requirements with their relevant issues. You can link single as well as multiple requirements with an issue.
Requirements can be linked to issue through the Requirements tab of Issue.
Steps
1. Open the Issue details page.
2. Open the Requirements tab.
3. Click on the Link button.
4. It opens the screen with requirements.
You can select requirements on the grid to link to 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.
Project: You can link requirements from across projects. Select the Project the requirements of which you want to link with the issue. You can link requirements from multiple projects.
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 them before moving to Project 2. Else, all the selection of Project 1 will be wiped off.
A. Linking a Single Requirement: Click on the Link 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.
The selected requirements are linked to the issue. The linked requirement records are shown on the screen.
If requirements from other project are linked, then the requirements show Entity Key of the corresponding project.
To view the requirement of other project, click on the Requirement Entity Key. It opens the test case detail page in the respective project and will change your current project.
Unlink Requirements
Go 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 you want to unlink from the issue and click on the Unlink Selected button.
Attachments
Users can also view, download, and add attachments in QMetry.
Comments
Users can also view, add, edit, delete Azure comments (Discussions) in QMetry.
Add Issues / Bugs / Defects
A. Steps to log issue from Issue Module to Azure
1. Open the Issue module.
2. Click on the New button on the toolbar. The Create Issues screen opens next.
3. Select Azure Instance.
Logging an issue for the First Time
You will be asked for Azure authentication through pop-up.
Enter Azure API Key to authenticate the user.
To Edit/Revoke Authentication
If your Azure credentials are changed, then follow Revoke Authentication to modify the credentials in QMetry.
4. Select Azure Project and Work Items.
Issues added from Issue module or from the Execution screen will be created in Azure only.
Users can click on the External Key in the Issue module, which opens the issue detail page in Azure, while the Entity Key opens issue detail page in QMetry.
The issue details to enter depends on whether you are adding issues in internal tracker of QMetry or in Azure.
If you do not have Azure configured with the project you are currently working on, then enter details in 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 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 inline editor to edit issue details.
Note: Azure issue State is a read-only field in QMetry and can not be edited.
Attachments and Comments
The following table describes what operations can be performed on Attachments and Comments when Azure is integrated with QMetry project.