How to create a requirements traceability matrix in Jira

By Jake Marsh · Updated

To create a requirements traceability matrix in Jira, install Tracestitch, have a space admin turn on tracking in Requirements > Settings and tick the work item types that hold requirements, then open the Traceability matrix tab. Each requirement gets a row with the work that implements it, the tests that verify it, open defects and a coverage verdict, built from the links already on your work items. Filter by folder or coverage, and click Export CSV to take it into a spreadsheet.

Why Jira needs help here

Jira lets you link a requirement to a story or a test, and a JQL search can list linked work items. It has no view that puts every requirement in one row with its implementation, tests and defects side by side, and no way to say whether a requirement is covered. Teams usually end up keeping that grid in a spreadsheet, which goes stale as soon as someone adds a link in Jira. Tracestitch builds the grid from the links themselves, so it is current every time you open it.

Steps

  1. Install Tracestitch from the Atlassian Marketplace in Jira Cloud.
  2. Open Requirements in the space's sidebar, then the Settings tab (space admins and Jira admins see it).
  3. Tick Track requirements in this space, choose the Work item types that are requirements and enter an ID prefix, for example PAY-REQ. Click Save. Existing requirements get IDs in creation order.
  4. Check how links are read. Under Linked work item types that are tests, the defaults are Test, Test Case, Test Plan and Test Execution. Under Linked work item types that are defects, Bug and Defect. Every other linked type counts as implementing work. If your space uses link types like "Implements" and "Verifies", tick them under Link types that count as trace links; with none ticked, every link type counts.
  5. Link your work as usual. Link stories and tasks to the requirement they deliver, and tests to the requirement they check. A test linked to a story that implements the requirement also counts, shown as "via" that story; you can turn this off in Settings.
  6. Open the Traceability matrix tab. Each row shows the requirement ID and title, Implemented by, Tests, Defects and Coverage.
  7. Filter it. Pick a Folder to see one area of the product, a Coverage verdict to see only gaps, or Only with links to review to see requirements whose text changed since their links were checked.
  8. Click Export CSV. Tracestitch shows the matrix as CSV text; select all, copy, and paste it into a spreadsheet or a .csv file. Up to 1,000 rows come out per run, so filter by folder for larger sets.

What the coverage verdicts mean

VerdictWhen a requirement gets it
Not coveredNo implementing work and no tests are linked
Tests onlyTests are linked, but nothing implements it
No testsWork implements it, but no test is linked
In progressBoth are linked, but some work or tests aren't done, or a defect is open
VerifiedAll implementing work and tests are done and no defect is open

Related requirements are listed on the requirement but don't count toward coverage.

An example

Say PAY-REQ-12 reads "Refunds over $500 need a second approver". It is linked to story PAY-341 (implements), test PAY-402 (verifies) and bug PAY-455 (open). Its matrix row shows PAY-341 under Implemented by, PAY-402 under Tests, PAY-455 under Defects and the verdict In progress. When the bug is closed and the story and test are done, the verdict becomes Verified with no one editing the matrix.

The matrix in searches and dashboards

Coverage is also a JQL field, so the same gaps appear anywhere Jira searches do. reqCoverage = "untested" lists requirements with work but no tests, and reqCoverage = "uncovered" lists ones with nothing linked. Save them as filters and add them to a dashboard. The Coverage tab counts requirements by verdict and by folder.

What it costs

Tracestitch is $10 a month for up to 10 users. From 11 users, every user is billed at $2.05 a month, with lower rates on larger sites. Atlassian bills it and there's a free trial. Pricing and the install link are on the Tracestitch page.

Tracestitch: Requirements and Traceability for Jira

Requirement IDs, versions and readable diffs on Jira work items. Baselines, a traceability matrix and suspect links after changes. From $10 a month for up to 10 users.


Questions

Can the matrix include tests from Xray or Zephyr?

Yes, when the test app stores tests as Jira work items. Add its test types under Linked work item types that are tests and linked tests show up with their Jira status.

Does the matrix only show work items I can see?

Yes. Lists and the matrix only show work items your Jira permissions let you browse.

Can I change the matrix columns?

The columns are fixed: requirement, implementing work, tests, defects and coverage. What lands in each column is set by the type and link lists in Settings.

Can I trace requirements across spaces?

Links to work items in other spaces are read like any other link, so a test in a QA space can verify a requirement in a product space.


More Tracestitch guides


More Jira guides