Skip to end of metadata
Go to start of metadata

The Traceability Tree (Custom Hierarchy) report offers you dynamic, broad-ranging traceability and test-case coverage statistics. Regardless of which Jira development items your team uses—epic, feature, story, task, etc.—and regardless of the hierarchy your team uses to structure and organize development work, the Traceability Tree report allows you a powerful overview of all testing coverage. The report even allows you to view and click links to associated test cases and bugs!

Here's an example of the data the Traceability Tree (Custom Hierarchy) report can show you. Notice how the report allows you to quickly see test-coverage gaps (items with no linked test cases), test-execution results, timestamps, and more.

Make the Report Work for You

Access the report by navigating to Reports > Traceability > Traceability Tree (Custom Hierarchy).

Make selections in each of the following fields to customize your report:


The project or projects for which you want to view coverage data. (See the note below for information about a known limitation of adding multiple projects.)

First Hierarchy Level

Use this field to specify the first hierarchy level you want to inquire on. The dropdown allows you to search and choose from any of your favorite JQL filters. This first-level filter is the only one required to generate the report, though additional levels may be added via Additional Hierarchy Levels.

Additional Hierarchy Levels

Specifies the additional hierarchy levels you want to inquire upon. Click Add Level and add as many issue types as you like, in any order.


Allows you to choose between results from only the most recent test executions or from all test executions.


Allows you to choose between a condensed display, which shows only high-level information for test-execution results, and a detailed display, which shows much more testing detail, including links to each test case, the date and time of the test execution, the name of the person who executed the test, as well as links to issues created during test execution.

The report generates the specific coverage information you selected via the fields. Extensive reports paginate every 25 items.

If you select multiple projects for the Traceability Tree report, test cases from projects other than the primary project (the first project listed) display as expected in the numeric Test Cases column, but test cases from non-primary projects do not populate additional details in any of the other report columns. This is a known limitation to the Traceability Tree report that the TM4J team will improve in future development. 

For example, you could potentially see a value in the Test Cases column that is not reflected in other columns, such as Execution Results.

Next Steps

Have a question for us?

  • No labels