| 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.
...
Issues
Requirements
Test Cases
Executions
Test Suites
→ Test Entities to view issue linkage report:
You can also generate report to view issues directly linked to test cases. If you create a new visual report using the Test Cases and Issues test entities, it will show issues directly linked to test cases.
To view report on issues logged from execution screen, you need to generate the report using Test Cases, Issues and Executions test entities. Refer to this article for more details.
Test Entity Fields
There are three types of entity fields:
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)
Notes:
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 filed field appears with the field type icon prefixed to it.
Internal Custom Fields can be identified with the “qmetry” prefix attach prefix 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.
...
Think Space (Create Data Table)
...
Go to QMetry Custom Gadget > My Gadget tab.
Click on the Edit icon for the gadget that you want to edit.
Once you are done with the changes, click Update Gadget button.
You can save the gadget with updated Gadget Name and Gadget Description.
...
Refer options as follows.
1. After clicking edit above, you can edit the gadget name.
2. Option to change filters.
3. Add Column, Group by, Labels, Filters, Operations and Values.
→ Group By can be applied to custom fields as well as system fields of type text, which includes lookup, multi-lookup, etc. Custom fields include of QMetry custom fields and external tracker fields that are synced to QMetry Insights.
...
4. Choose to change the report chart.
5. Re-generate report to view the changes.
6. Click “Update Gadget” to save changes.
...
Exporting Gadget Data
You can download the chart image in PNG, JPEG, SVG Vector and PDF formats.
...
You can also export all the dashboard gadgets through the API call. Refer to the link - API for Reports for more details.
| Child pages (Children Display) |
|---|