How to set up test traceability in Jira
Traceability answers one question: for this story, epic or release, which tests cover it and did they pass? Here is how to answer it in Jira.
Option 1: issue links and JQL (free)
- Ask a Jira admin to add a link type in Settings > Work items (Issues) > Issue linking, for example outward "tests" and inward "is tested by".
- Represent each test as an issue (for example a Test work type, see the migration guide) and link it to the stories it covers.
- Use the status of the test issue for its latest result and a filter or dashboard gadget to find gaps, for example stories in a fix version with no "is tested by" links.
This is free, but it gets heavy fast: each test is one issue with only one current status, there is no run history per release, and finding uncovered stories needs manual checks or an advanced JQL app.
Option 2: a test management app
Proofline keeps test cases, cycles and runs separate from your issues and links them to stories, bugs and epics. A panel on each issue shows its tests and their latest results, and the coverage report takes any JQL (an epic, a fix version, a sprint) and shows what is passing, failing, not run or untested. Results can come from manual runs or CI imports. When you need to share it, Pledona Export turns the linked issues into Excel or PDF. Proofline is free for up to 10 users and pending Atlassian Marketplace review.
Frequently asked questions
Does Jira Cloud have a traceability matrix?
Not built in. You can approximate one with issue links, filters and dashboards, or use a test management app with a coverage report.
How do I find stories with no tests?
With links alone this needs manual review or a JQL extension. A coverage report in a test management app lists untested issues for any JQL.
Should test cases be Jira issues?
It works for small teams. Larger suites usually keep tests in an app so runs and history do not clutter boards and issue counts.