qTest Insights provides the ability to build custom reports based on custom Site Fields which users create from qTest Manager.
Please note that Insights supports cross-projects reports, so Insights only pulls site-level custom fields from qTest Manager. Your custom fields should be set up at site level in order to be pulled.
Insights will pull in custom site fields into following explore data areas:
- Test Cases
- Test Runs
- Test Run Logs
- Defects (qTest).
The following example is to describe the typical flow from creating a custom site field, including it in a template, add the mapping a project to the template, and finally showing fields in Insights' explore data reports.
See the Site Fields article in for a step by step guide on setting up site level fields for your qTest projects.
- Create site-level custom field "SampleCustomField" for object "Test Run"
- Create a template and enable that custom field "SampleCustomField" in the template
- Add project into the template
- Go to the project, create a Test Run with custom field "SampleCustomField"
- The custom field "SampleCustomField" is automatically populated to Insights' Explore Data/ Test Runs report
- The custom field is hidden by default. Select the checkbox to make it display in the data grid.
How to quickly know if your custom fields in your project are site fields and eligible to be pulled into Insights, check Field Settings of your Project. The fields which are marked as both "CUSTOM" and "SITE FIELD" will be pulled into Insights Explore Data reports.
For example: In the following screenshot, the fields in highlighted rectangle will be populated into Insights' Explore Data/ Test Cases report.
When a site-level custom field is deleted/updated from qTest Manager, that change will not automatically to Insights Explore Data Report. You may need to access another Explore Data report then open that report again for the grid layout to be fully reset.