Projects using Azure integration for Issue (Bug) Tracking
Note
This document applies only when project is configured with a Azure project.
The Issue module provides bi-directional integration between and JIRA. You can create, view, and edit issues in , and the changes sync to JIRA. Likewise, issues added or updated in JIRA appear in .
You can perform the following tasks in the Issue module:
View, Add, Modify Azure issue details, comments, and attachments.
Map Azure custom fields with .
Access issues logged during test execution in the Issues module.
After integrating project with Azure:
The system do not display issues added from Issues module before integration in the Issue grid.
Internal issues created and linked from the Execution screen before Azure integration are displayed in read-only mode.
Clicking an internal issue linked from the execution screen, opens the detail window in read-only mode.
Viewing and Organizing Issues
Click the Issue Entity Key in the grid view to open the issue detail page.
You can customize the grid view by resizing columns, organizing tabs, or applying filters and sorting. To learn more, refer to Manage Grid Columns.
In the issue module, there are individual tabs for - Details, Execution Runs, Requirements, Attachments, and Comments.
Details Tab
The Details tab displays information synced from 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 the list of Azure tags in .
Stack Rank: View the list of Azure in .
Effort: View the list of Azure in .
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 the Azure workflow Status of the 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 the description for the issue in plain text.
Azure Custom Fields: View Azure custom fields, if any.
Created Date: The date on which the issue was created in Rally.
Changed Date: The date on which the issue was updated in Rally.
Note
Watcher, Owner, and Assigned Release are not available for projects integrated with Azure.
Execution Runs
Issues logged from the Test Executions module are displayed here.
Execution Time and Remaining Time
To view the execution time and remaining time:
Open the Issue Detail page.
Go to Execution Runs tab.
View Execution Time and Remaining Time calculated for the test execution.
To view Execution Time and Remaining Time for test execution, open the issue detail page and go to the Execution Runs tab.
 |
The columns Execution Time and Remaining Time are added to the grid in the following locations within the application:
In Test Executions tab under Test Suite detail page.
In Test Executions tab under Test Case detail page.
In Execution Runs tab under Issue detail page.
Calculation of Execution Time of a test suite:
The system calculates the Execution Time of a test suite based on Estimate Time of all the test cases in that test suite.
Calculation of Remaining Time of a test suite:
After the test suite is executed, the system calculates the Remaining Time for all “Not Run” test cases. Test cases with a “Failed” or “Blocked” status are also included, as work is still pending on them.
Linking Requirements to Issues
You can link individual or multiple requirements to issues using the Requirements tab on the Issue page.
To link requirements, perform the following steps:
 |
Open the Issue details page.
Go to the Requirements tab.
Click the Link icon to attach an individual requirement or select the requirements and click Link or Link & Close.
Select the requirements. Use filters, including Labels and Folder Paths, to narrow down the list.
Click Link & Close.
Project Selection:
You can link requirements from multiple projects. Select the project containing the requirements to link.
To link requirements across projects, select a project, link its records, then switch to the next project. Remember, switching projects clears previous selections, so click Link before moving on.
The linked requirements are displayed on the screen. If a requirement belongs to another project, its Entity Key is shown. Clicking the Entity Key opens the requirement in that project and switches you from the current project.
Unlinking Requirements
To unlink a requirement, perform the following steps:
Go to the Requirements tab of the issue.
To unlink a single requirement, click the Unlink icon for the requirement. The requirement is unlinked after confirmation.
To unlink multiple requirements, select the requirements you want to unlink from the issue and click on the Unlink Selected
Attachments
You can view, download, and add attachments in . Refer to Managing Attachments to know more.
Comments
You can also view, add, edit, and delete Azure comments (Discussions) in . Refer to Add Comments to know more.
The table below describes the operations available for Attachments and Comments when Azure is integrated with a QMetry project.
Operations | Attachments | Comments |
|---|---|---|
Can be added while creating an issue? | Y | N |
Can be added while editing the issue? | Y | Y |
Can be Edited? | NA | Y |
Can be Deleted? | N | Y |
Logging issues from Issue Module to Azure
Open the Issue module.
Click New.
Select the Azure Instance.
Select the Azure Project and Work Items.
Issues created from the Issue module or Execution screen are displayed in Azure. In the Issue module, click the External Key to open the issue detail page in Azure, or click the Entity Key to view it in . The details you enter depend on whether you are adding the issue in the internal tracker or in Azure:
If Azure is not configured: Enter details in fields.
If Azure is configured: The Add Issue screen includes Azure-specific fields that you need to fill in.
Defects can be added from both the Issue module and the Execution screen in .
Fill in the following details:
Summary: View the issue summary.
Priority: Check the issue priority as listed in Azure.
Work Item Type: View the synced issue type.
Tags: See the Azure tags in .
Stack Rank: View Azure stack rank in .
Effort: View the Azure effort list in .
Assigned To: This field shows the Azure assignee.
Area Path: Select the folder path from Azure.
Iteration Path: Choose the folder path from Azure.
State: View the Azure workflow status (read-only).
Created By: Displays the Azure user who reported the issue.
Team Project: Read-only field synced from Azure.
Description: Enter a plain text description of the issue.
Azure Custom Fields: View any Azure custom fields.
Link Attachments: Attach files during issue creation.
Logging issues from the Execution screen of the Test Suites Module
You can log issues at both the test case and test step levels, including in bulk.
Open the Execution screen.
Click the bug icon next to the test case or test step to log an issue. For more details, refer to Adding or Linking Issues to Test Case and Test Step
Creating Issues at the Step Level for Automated Test Cases
During an automated test run, if an error occurs, the system shows an Error Message and Trace on the test execution screen. When users create an issue at the test step level, the systemautomatically attaches a .txt file with the Error Message and Trace to the issue.
On opening the issue in , the Attachment tab shows the .txt file attached to it which contains the Error Message and Trace.
Create Requirement from Issue
To create a requirement from an issue:
Select the issue and add a new requirement.
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:
From the Toolbar: Select an issue in the grid pane, click "Add" on the toolbar, point to "From Issue," and select "Requirement."
From Context Menu: Right-click an issue in the grid pane, point to "From Issue," and select "Requirement."
Map Azure custom fields with
System fields are auto-mapped and read-only. You can select the custom fields that appear in the Issue module. To make the Reporter field mandatory, enable the corresponding flag.
Deleting an Issue
You can not delete Azure issues from . If a user deletes an issue from Azure, it also gets deleted from and its linkages to the test cases or test steps are removed.
Removing an Azure Configuration
On removing the integration of Azure project, all the issues created from Issue module into Azure are not displayed in the Issue module in .
For Azure issues logged during execution, the association of these issues with respective test cases or test steps are removed.
Issues created in the internal tracker before Azure integration are displayed in the issue grid.
Edit or Revoke Existing Azure Authentication
The Azure Authentication window initially appears when adding an issue for the first time to request Azure credentials. This window does not reappear for subsequent operations unless credentials are revoked.
To display the Azure Authentication window again when creating or editing an issue, revoke the existing Azure credentials:
Go to Integrations.
Click the cog icon and select Revoke credentials.
Edit Issue Details
Once the issues are added, open the Issue details page to view or edit the details.
Note
Users cannot edit the field values of the Work Item Type and State fields of external issues. The fields appear in read-only mode.
Delete Existing Azure Integration
If the Azure Integration configuration is not required anymore, then you can delete the configuration.
Go to Integrations.
Open the cog icon and click Delete for the configuration to delete.