Traceability matrix

At the beginning, there is a list of requirements

We recommend adjusting the search query to only display requirements you are interested in. For example, if you want to filter on the prefix "REQ-", use: key ~ 'REQ-%'.

Add columns to your report

You can add columns using the cog menu:

You can end up with the properties of each requirement. Note the "tree view" on the left, which lets you drill down into requirements.

Connect to Jira

If you have requirements attached to Jira issue, they can be included:

Of course, each Jira field can be displayed in the matrix in Confluence:

All of these options are available using the cog menu:

And if you Jira issues are linked to Jira issues:

This matrix can really gather a lot of information, and we recommend using it a lot.

Jira Cache (New in 3.1)

Jira integration is now faster since you can benefit from a cache.

As a user, the data you are seeing in the matrix is kept during 5 days.

Type of data cached:

• Jira issues
• Epic links
• Team from Portfolio
• XRay data
• Zephyr data

The user can empty his cached data by using the checkbox next to the "Get data from Jira" existing checkbox.

Limitations

• We don't have calculations yet. You can't display the percentage of children in a given status, for example. It can't be used to display % coverage, for example.
• We don't have filters,
• We may not have all Jira fields, but we've already developed renderers for Xray fields (Xray integration with Requirement Yogi) and we could do it for you too.

We practically have everything else.

List of supported Jira fields in the traceability matrix