Creating custom reports using external trackers (like Jira, Azure, or Rally) custom fields in QMetry Insights

With the release of QMetry v8.12.1.1 it is possible to create custom reports containing custom fields of external trackers (like Jira, Azure, or Rally) synced with the QMetry projects.

You can now create reports containing fields of external trackers (like Jira, Azure, or Rally) that are mapped with the Requirement and Issue module of QMetry. Here’s how you can do it:

  • Go to Projects > Project/Release/Cycle > Edit your project > Integration tab > expand the integration URL > click on the “Action” icon to open “Edit Jira Fields Configuration” to enable the custom fields (to display on UI) of external tacker issue types that are associated/map with the Requirement and Issue Module of QMetry. Refer to the below screenshot:

Note:

  • Only the custom fields that are enabled under “Edit Jira Fields Configuration” will be available in QMetry insights to create reports.

  • If you do not see your fields here, do ensure the fields are added on Jira’s “create issue” screen.

(IMPORTANT) - To be able to create Custom reports containing their external tracker's fields, the “Sync fields to Reports“ flag should be enabled to Sync the mapped external custom fields to QMetry Insights (attaching a screenshot below for your reference). System administrators can configure this setting to sync and make them available to display the external tracker's fields in the QMetry Insights - Visual Report entities and Advanced Query Report tables.

The external Custom Fields mapped with the Issue module will be covered under the “issueextudf” table. The external Custom Fields mapped with the Requirement module will be covered under the “requirementextudf” table.

  • For example, an external custom field “Sprint” is mapped with the Requirement module in Project > Integrations tab. This mapped field is then synced in the QMetry Insight tables using the Sync fields to Reports feature. The field will be displayed as “ext_sprint” under the requirementextudf table. Refer to the below screenshot.