Tips for working with Report Builder traceability reports
In traceability reports, use relationship conditions to get different results
For example, if you want to see the test coverage for requirements in a project (which requirements are validated by a test case), the condition you select for the link type determines the results that you see:
- Required: Shows only artifacts that have the relationship that you specify.
- Does not exist: Shows only artifacts that don't have the relationship that you specify. For example, use this option to see gaps in test coverage.
- Optional: Shows all artifacts regardless of whether they have the relationships that you specify. For example, show all coverage, gaps, and links.
When you combine reports, "Merge" is not always the best option
When you combine two traceability reports, merging the results might not always show the data that you need in the best format. In each traceability path, if your source artifact is linked to several related artifacts, avoid using the Merge option to combine the data. Instead, consider appending the second path.
About this task
- Work items that are related to Story 83
- Requirements that are implemented by Story 83
Create a report of work items that are related to Story 83.
http://<server_name>:<port>/rs. On the Reports page, click Build report.
Choose a report type.
- Use the default data source that is configured for your environment, or click the pencil icon , and select a different one from the list.
- Select the Current Data check box.
Limit the scope of your report by selecting which projects to report on.
Select the Requirements Management (RM) and Change and Configuration Management (CCM) project.
Choose an artifact.
Under Change and Configuration Management, expand Work Item, and select Story. Then, click Continue.
Trace relationships and add artifacts.
In this section, create links from the story artifact type to the related work items. Click Add a relationship and, under Work Item, select Children and Related. Click OK. Select Work Item and click OK.The traceability path looks like this:
Set conditions to focus on Story 83.
Click Add condition, and for the story artifact type, set the ID attribute to is 83.
Name and run the report.
Story 83 has 11 related and child work items.
- Open Report Builder.
Create a report of requirements that are implemented by Story 83.
Complete the steps from the previous procedure to create this report. The traceability path looks like this:The results show that 10 requirements are implemented by Story 83.
Combine the two reports by using the Merge option.
Open the first report and edit it to add a second traceability path.
In the Trace relationships and add artifacts section, select the check
box to enable multiple paths and click Add a relationship to create the
second traceability path.
Select the Merge option and click OK.
Click Add a relationship and select Implements
Requirements. From the list of artifacts, select
The traceability paths look like this:
Run the report and review the data.
Because Story 83 has 11 related and child work items and it also implements 10 requirements, the merged report shows 110 items. Each possible story-work item-requirement relationship is listed. The results are hard to read.
- In the Trace relationships and add artifacts section, select the check box to enable multiple paths and click Add a relationship to create the second traceability path.