| Table of Contents | ||
|---|---|---|
|
...
In QMetry Insight, you can see the list of tables and their fields on the left panel. The panel contains the consolidated QMetry data in just 15 tables which are synced in real-time. For making the query creation easier, the names of the tables have resemblance with QMetry test assets and different modules.
Note: In Requirements and Issues tables, field names having "Jira" as prefix are renamed with “Ext” prefix. For more details refer this page.
...
Here is a quick overview of tables available as part of the report schema and the kind of data stored on it :
| Table Name | Details |
| issues | Details of QMetry and external issues. |
| issuecycle | Details of cycles associated with issues. |
issueextudf | Details of custom fields of external tracker mapped with the Issue module. The table is available only if you have opted for the Advanced Reports App. |
| requirementissue | Details of issues linked with requirements. |
requirementextudf | Details of custom fields of external tracker mapped with the Requirement module. The table is available only if you have opted for the Advanced Reports App. |
| requirementreleasecycle | Details of release and cycle associated with a requirement version. |
| requirements | Details of QMetry and Jira requirements. |
| requirementtestcase | Details of Testcases linked to requirements. |
testcaseissue | Details of issues directly linked with test cases without execution. The table is provided to enable the creation of reports containing defects linked directly to the test case. |
| testcasereleasecycle | Details of release and cycle associated with a test case version. |
| testcases | All the test case details. |
| testcasetestsuite | Details of test cases linked with test suites. |
| testexecutionissue | Details of issues found during executions. |
| testexecutions | Testcase execution details. |
| teststepexecution | Execution details of a Test case - steps. |
| teststeps | All the details of test case - steps. |
| testsuitereleasecycle | Details of release and cycle associated with test suites. |
| testsuites | All the test suites details. |
| users | All the details of users. All ids like createdBy, owner, executed by, etc will be mapped with `users` table to get the username, userAlias, fisrtname, lastname etc. |
...
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. Additional tables related to UDFs will be displayed. 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 “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 “ext_release_reference” under the requirementextudf table.
...
You can also export all the custom dashboard gadgets through the API call. Refer to the link - API for Reports for more details.
Best Practices
- Rights to write custom queries must be provided only to those users who have knowledge of writing SQL queries and can access any QMetry data, as there is direct access to all QMetry data in Report Schema DB.
- The custom SQL queries must always include a project filter specified as : @FILTER.PROJECT. This will prevent the recipients of the shared report gadgets from inadvertently viewing data from other projects that they do not have access to.
- The custom SQL report queries after creation must be run and saved against a Sample Project, so that the report does not load with the data of an un-intended project.
- The Report DB has tables like testcase, testexecutions, etc. which now only have user IDs instead of the actual information of the users. This information should be queried by writing an SQL Join with user IDs from `users` table now available in the Report DB schema.