Traceability
Show the path of the testing process from the start to the end with Traceability reports.
Traceability reports provide a clearer picture of how testing efforts are aligned with specific requirements. By demonstrating the relationship between requirements, test cases and defects, they help with tracking the progression of tests from the start to the end. With traceability reports, testing teams can trace the root of defects faster and understand the impact of changes.
In ATM, Reports can be accessed in the Testing Hub. At this moment, users can choose to create two types of Reports - Traceability and Test Coverage.
Creating a Traceability Report
In order to start generating the Traceability Report, go into Testing Hub > Report Design.

Select Traceability Report.

In the new dialog, select the Testing Project, based on which ATM will generate the report.
Users can also access information about the configuration of projects in the Testing Project, such as project name, project key and configured work types for selected testing elements.
Users can use JQL syntax to narrow down the Requirements scope that is taken into consideration when creating the report, e.g. to report on Requirements with a status 'Accepted'.

To finish, click Generate the report.
Traceability Report View

Once generated, users can immediately see the assessment. The panels at the top allow to quickly overview crucial information related to the report itself, such as:
Testing Project details
regarding the Testing Project used in the Report
Coverage of Requirements
covered Requirements are ones with linked Test Cases
Assignees
appearing in testing elements of the Report
Test Case Executions
insights to the progress of Test Case Execution (TCE) objects that appear in the Report
the toggle Show latest TCEs allows users to include in the Report only recent iterations of TCEs
Defects
total number of Defects
the average amount of Defects per Requirement
In the table below the panels, users can view listed Requirements along with related testing elements in the neighboring columns:
Test Cases
Test Case Executions
Defects
For each testing element, following information is listed:
Work-key
Summary
Status
Additionally, for each of the Test Case Execution objects, users can quickly access following information:
TCE Status
ATM Environment
Assignee
TCE Progress
Link to the Test Execution, where TCE appears
Link to previous iterations of the TCE
Layout configuration

The contents of the table can be adjusted to the needs of the users and customized. In order to modify the layout, click the Configure layout button. In the Configure layout window, in the Work Item Layout tab, select fields that should appear in the table for each of the testing elements (Requirements, Test Cases and Defects). The default fields are always visible and cannot be removed.

The users can add maximum 3 custom fields, from the following selection:
Requirements
Components
Fix Version
Sprint
Labels
Priority
Test Cases
ATM Environment
Components
Fix Version
Sprint
Labels
Priority
Defects
ATM Environment
Components
Fix Version
Sprint
Labels
Priority
In the same dialog, in the Testing Objects tab, users can also configure the testing elements that will be visible in the report.

The options are:
Select all (where all columns with all objects will be visible)
This is the default option.
Only Requirements and Test Cases
Requirements, Test Cases and Test Case Executions
After selecting the options, the view of the Report will be automatically updated.
Exporting the report

Users can directly export the Traceability report to PDF or CSV format with the Export button. The generated file includes all items and selected fields currently visible in the report.
Last updated
Was this helpful?
