| Table of Contents | ||
|---|---|---|
|
Introduction
QMetry Insight gives you interactive reports that can be altered to get detailed insights by drilling down to the data. These reports also provide the facility to navigate, filter, sort, and view the data.
...
ID Fields: These are numeric fields not displayed on UI. The dynamic filters are mostly applied on ID fields. Like Project ID, Release ID etc(Denoted as A)
System Fields: These are system fields that are visible on UI. These fields are mostly displayed in the report. Like Project Name, Release Name etc (Denoted as B)
Custom Fields: Fields with “qmetry_” prefix custom fields. (Denoted as C)
NoteNotes:
If you have opted for the Advanced Reports App: Custom Fields (of Requirements and Issue modules) which are mapped with Jira, Rally and Azure will be displayed in QMetry Insight tables if the Sync fields to Reports feature is turned “On” on the Integrations tab in the Integration module.
If you have not opted for the Advanced Reports App: Custom Fields (of Requirements and Issue modules) which are mapped with Jira, Rally and Azure will not be displayed in QMetry Insight tables. Only QMetry Fields data and
external tracker System Fields data which are synced will be available for generating reports.
Search field is provided to easily locate the required field for the module. Each field appears with the field type icon prefixed to it.
Internal Custom Fields can be identified with the “qmetry” prefix attach to the fields.attached to the fields.
External Custom Fields can be identified with the “ext” prefix attached to the fields.
For example, an external custom field “Release Reference” 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 “Requirement ext_release_reference”.
...
Note: Records shown are only for the latest version of the test asset. For all version data switch to Advance Query Reports.
...