Clearlane
EN
FrançaisDeutsch
Solutions

By need →

Clearlane for QualityClearlane for CyberProject controlValidation support

By industry →

Pharma and biotech (GxP)Medical devicesFinancial services (DORA)Software and IT (ISO 27001)Manufacturing (ISO 9001)
Apps

For Jira →

DeliveryForecastBudgetGanttPulseCAPACRATestsBreach & Incident ReportingRisk Register

For Confluence →

Controlled DocumentsRead & UnderstoodAnswersFresh

Jira dashboard gadgets →

Created vs ResolvedThroughputCumulative FlowSprint BurndownVelocityWIP AgingCycle Time
Trust centerGuidesSupport
Guide · 5 min read

Test traceability matrix in Jira: link requirements, tests and results

A traceability matrix answers one question an auditor always asks: is every requirement really tested, and did the test pass on the version you shipped? Here is how to build one in Jira that stays true without a spreadsheet, including for IEC 62304 medical device software.

What the matrix must show

  • Each requirement, with its Jira work item.
  • The test cases that verify it, one or several.
  • The latest result of each test, on a named version: passed, failed or not run.
  • The defects raised by failed tests, and whether they are closed.

A requirement with no test, or with only old results, is a gap. The matrix is there to make those gaps visible before the auditor does.

Why spreadsheets drift

A matrix kept in a spreadsheet is right on the day it is filled in. Requirements change, tests are added, a run fails, and nobody updates the file. Keeping the links where the work happens, in Jira, means the matrix is rebuilt from the real data every time you open it.

For IEC 62304 teams

IEC 62304 expects you to show that software requirements and risk control measures are verified, and to keep traceability between them and their tests. In practice, the auditor picks a requirement or a risk control and follows the chain: requirement, test case, test run on the released version, signature. Prepare that chain for each release, and keep the test report with the version.

A simple routine

  1. Write the test cases from the requirements, and link each one in Jira.
  2. Run them step by step for the version under test; a failed step becomes a Jira bug.
  3. Check the matrix before release: no requirement without a passed test, no open blocking defect.
  4. Sign the campaign and keep the PDF report with the release.

Our free test plan template includes a traceability table to start from.

Where Clearlane Tests helps

Clearlane Tests keeps test cases, step-by-step runs and the traceability matrix in Jira. A failed step becomes a bug in one click, and each campaign can end with an electronic signature and a PDF report. It helps you produce the evidence; it does not decide for you whether a release is safe.

See Clearlane Tests on the Atlassian MarketplaceHow it works