Page History
...
The template contains 4 tabs, the following tables show an example of the columns/rows you should expect.
How to use
This report can be generated from different places/contexts, including:
...
| Info | ||
|---|---|---|
| ||
| General information about all the existing places available to export from and how to perform it is available on the Exporting page(DC, Cloud) page. |
Source data
In the store, you can find 2 subtypes for this template:
...
from the Issue Navigator/Search, search by the issueType (i.e., "Test Execution") from your project (e.g., "BOOK") and then use bulk export or Export->XporterExport→Document Generator
| Code Block | ||
|---|---|---|
| ||
project = "BOOK" and issuetype="Test Execution" order BY created DESC |
...
- from the Issue Navigator/Search, search by the release (i.e., "fixVersion") of your project (e.g., "EWB") and then use bulk export or Export->Xporter>Document Generator
| Code Block | ||
|---|---|---|
| ||
project = "BOOK" and issuetype= "Bug" and fixVersion=1.2 order BY created DESC |
...
from the Issue Navigator/Search, search by Test Executions or Bugs assigned to that Test Environment (e.g., "chrome") and then use bulk export or Export->Xporter>Document Generator
| Code Block | ||
|---|---|---|
| ||
project = "BOOK" and issuetype in ("Test Execution", Bug) and environment IS chrome order BY created DESC |
...
You can further finetune the content and formatting via JavaScript,you can find more useful snippets in this tutorial for Xporter and DocGen as well as Xporter documentation (Cloud, DCDocument Generator (DC, Cloud).
Exercise 1: extend the report to custom issue types
...
The number of Defects and associated items, depending on scenarios, can be considerably high, especially with CI/CD. As this report sums up quite a lot of information, please use it wisely.
...
| title | Some tips |
|---|
...