Back to QMetry All Products Help Page
Map Azure Projects, Issue type and Fields with QMetry Project
Map Azure Project with QMetry Project
Note: The Azure project, in which the user has project administrator rights, can be integrated with the QMetry project.
Map a Single Azure Project with QMetry Project
These steps have to be performed in QMetry by Login as QMetry Project Admin :
Go to Projects > Project/Release/Cycle
Open the Project > Integration tab.
Select the Azure URL with which this QMetry project mapping has to be done.
Select the Azure project to configure with this QMetry Project.
Once the project is selected, select Issue Type <> QMetry Module associations. The issue type is a multi-select list. If the requirement is mapped, select the folder to import requirements.
Click on Save and Activate.
Map multiple Azure projects from a single Azure instance with one QMetry project
QMetry allows multiple Azure projects to be configured with one QMetry project. Below are the steps for the same :
Go to Projects > Project/Release/Cycle
Open the Project > Azure Integration tab.
Select the Azure URL with which this QMetry project configuration has to be done.
Select the Azure project to configure with QMetry Project.
Map Azure Issue Types to QMetry Modules.
Map Azure Issue types to QMetry modules
Once the project is selected, if you are managing your project requirements as Azure epics, you should select the Issue Types "Epic" to be associated with the Requirement module. Selection of Issue Type is a multi-select filter, which allows you to select multiple issue types and map with the Requirements module. Selection of the folder where the imported issues will be created is mandatory. The first time sync will import all the issues to the selected folder. These issues can, later on, be moved to other folders in QMetry where any changes done to the issues will be synced. However, all the new stories and epics that are not part of QMetry will be synced into the selected folder.
To map issue types like bugs or tasks to the Issue module, users can select the Issue Types associated with the Issue module. This is a multi-select filter. The issue types that are mapped with the Requirement module can not be mapped with the Issue module and vice-versa. The issues that would be imported and synced with QMetry, would be visible in the Issue module with the external key indicating the Azure Issue Key.
Click on Save and Activate/update once the configuration is done. ("Update" if Azure integration was already Saved and Activated for the QMetry project.)
Go to Integrations and check the syncing of Requirement, Issue and Metadata is completed.
Map multiple Azure projects from multiple Azure instances with one QMetry project
QMetry allows multiple Azure instances to be configured with one QMetry project. Below are the steps for the same:
Go to Projects > Project/Release/Cycle
Open the Project > Integration tab.
Select the Azure instance with which this QMetry project configuration has to be done.
Configure the projects > Save and Activate the Integration.
Once the project is selected, select Issue Type <> QMetry Module associations. The issue type is a multi-select list. If the requirement is mapped, select a folder to import requirements.
Select another Azure instance from the Azure Instance list.
Configure the projects > Save and Activate the integration.
Once the Project is selected, select Issue Type <> QMetry Module associations. The issue type is a multi-select list. If the requirement is mapped, select a folder to import requirements.
This way you can integrate multiple Azure instances with QMetry Project.
Map QMetry Folder to Import Requirements
Project Admin has to select a folder of their choice during Azure configuration to import requirements from Azure into QMetry. Requirements already imported earlier will remain intact in their respective folders. New requirements will be imported in the folder selected during Azure configuration.
If the user changes the already set folder, then a pop-up appears asking for confirmation on changing the destination folder for new requirements that are being imported. The impact will be -
Only new requirements will be moved to the synced folder.
Requirements imported earlier will remain in their assigned folder only.
Copy / Move the Synced Folder
On Copy/Move Folder, it will move the folder to the new folder and update folder mapping on the Project screen as well.
Archive Folder
Folders with external entities in it can not be archived. Users can move the imported requirements to other folders and then can archive the folder.
The folder that synced during Azure integration for import of requirements can not be archived.
In the bulk archive folder, the folders having external entities will be skipped. Sub-folders of this folder will also be skipped from the bulk archive even they do not have external entities in them.
Change Mapping of Issue Type with Requirement module
Scenario 1. Issue Type mapped with Requirement is replaced with another Issue Type
Issues synced based on the earlier mapping will be converted into internal issues and they will no more be Azure issues.
New issues will be synced as requirements as per the changed Issue Type.
Scenario 2. In addition to the existing Issue Type, another Issue Type is mapped with Requirement
Issues synced based on the earlier mapping will remain intact as Azure issues.
New issues will be synced as requirements as per the added Issue Type.
Configure Custom Azure fields for QMetry Module
QMetry displays default Azure issue fields in QMetry Modules. Project Admin can choose to display Azure custom fields as per project needs. Configuration of custom fields has to done separately for every configured Azure Project and Issue Type.
The following Azure field types are supported in QMetry:
Number
Date
Date and Time
Single line
Multiline
Multi Look Up Option
Single Look Up Option
User picker
Multi-user picker
Version picker
Multi-version picker
Below are the steps :
Note: In case QMetry does not display the Azure field in the configuration screen - "Sync" project data to configure the field.
Configure custom fields for Requirements and Issues.
Sync Azure data to QMetry. For example, newly created custom fields, etc.
A. Sync All: It will sync all issues irrespective of their updated-date.
B. Sync: It will sync only those issue values which are recently updated in Azure based on their updated-date.
You can sync the mapped Azure custom fields in the QMetry Insight module for Visual Reports and Advanced Query Reports. Read more about Sync fields to Reports.
Note: At least one of the Azure Project should be integrated with the Issue Module. Once Azure is integrated with the QMetry project, the internal issue module will be disappeared from the QMetry project.
View Azure Integration Status
Users can view all the integrated Azure instances, their associated QMetry projects, and their current Status - either Active or Inactive.
The Integration tab gives you a quick idea of the status of Azure and QMetry project integration.
Steps
Expand Integration on the sidebar menu and select Azure Integrations. There are two tabs on the screen: Integration and Azure Scheduler Status.
Open the Integration tab.
Back to QMetry All Products Help Page