Page History

...

• see all the Test Runs for a given Test , or a Test Execution, or a Test PlanExecution, Test Plan, Test, Test Set, or Story
• see the failed Test Runs and understand what happened and its impacts at high-level
• see the defects linked to failed Test Runs
• see the requirements linked to failed Test Runs
• see the failed Test Runs that have no defects
• track the Test Runs that are taking most time

...

This report is applicable to:

• 1 or more Test Plan issues
• 1 or more Test Set issues
• 1 or more Test Plan Execution issues
• 1 or more Test Execution issues
• 1 or more Story issues
• a combination of the previous

Please note: to avoid redundancy in the output, we recommend not mixing source types, especially if the entities are also linked with each other (e.g. passing the issue keys for Stories and Test Executions linked to them to the template at the same time)

Output format

The standard output format is .XLSX, so you can open it in Microsoft Excel, Google Sheets, and other tools compatible with this format. From those tools you may be able to generate a .CSV file.

...

1. Issue types having these names
   1. "Test", "Test Set", "Test Plan", "Test Execution", "Story"

If any of these assumptions is not met, you need to update the template accordingly.

...