Traceability Report [PLUS]

Traceability Report allows you to track the connections among tests, test executions, and bugs over a selected time period and within a selected project or JQL filter. This helps you assess the condition of the system you are testing and identify areas that might require special attention.

You can also see how requirements connect with test cases. This can help you visually assess test coverage in your project and identify which requirements still need more test cases or fuller coverage.

How to open Traceability report

Data Center
To view the Traceability Report, click Reports in the Jira project menu, then find Test Traceability Report in the Other section. You can also open the Traceability Report from Apps → QAlity page.

Cloud
To access the report, go to Apps → QAlity Plus → Traceability report.

Bugs Traceability

To view the Bugs Traceability report, set Trace from to Test cases in the filters, apply the desired filters, and click Generate report:

The Bugs Traceability report shows all test cases from the selected project or JQL filter. The second column provides useful information, such as how many times a test case was executed, what the execution results were, and when it was last executed.

To look at a test case's execution history in more detail, click the number in the Test executions column to open its history. You can also click the Last execution date to open that execution.

The last column provides a summary of bugs found in those test executions and their statuses. To see more about the linked bugs, expand the list to view their titles and statuses.

Requirements Traceability

To view the Requirements Traceability report, set Trace from to Requirements in the filters.

If you want to view data from a single project, choose the work item type you want to display.

To analyze requirements from multiple projects, create a JQL filter and select it instead of a project. After you apply all the desired filters, click Generate report.

The first column of the report contains all requirements. If you use a JQL filter, it shows all work items that match that filter. The next column lists all test cases linked to each requirement. This way, you can check which of your requirements have test coverage.

Next to each test case, you can see its execution details, as described in the Bugs Traceability section.

How to filter

Unresolved test cases only

You can filter by active test cases. This means that only test cases without a resolution are displayed. By "resolution," we mean the native Jira workflow resolution. This lets you focus on test cases that are actively used or in progress, instead of viewing every existing test case.

Test Type [QAlity Plus Advanced]

Use this filter to view and analyze only a specific test type.

Traceability report export

You can export the report to share it with a client or present it to senior management. Click the Export icon to download the generated report as an Excel (.xlsx) file. The file includes only the report that is currently displayed.

In the exported file, bugs are displayed across multiple rows:

Traceability report export limits

A single Traceability report export can cover a limited number of items. The limit depends on what the report is traced from:

A report is treated as traced from a requirement when Trace from is set to Requirement and either a
requirement type or a Jira filter is selected. Otherwise, the test case limit applies.

Why the limit exists

An export pulls every matching test case, its executions and all linked bugs from Jira. Large exports consume the Jira API rate limit that is shared by all QAlity users on the instance, so several large exports in a row can exhaust the hourly quota for everyone. https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

The Export button is disabled when the report that is currently displayed is over the limit. Hovering it
explains why:

This report contains more than 20000 test cases. Narrow the filters and generate the report again.

Change the filters and press Generate report to re-evaluate.

To get the export through, narrow the report first, for example by:

• shortening the execution date range,

• selecting fewer test cycles, statuses, or test types,

• picking a single project instead of a Jira filter that spans several,

• limiting the report to active test cases only.

Do you have any questions or feedback? Feel free to contact us here 💡