👉 Available on Business, and Enterprise plans.
The traceability report shows which external requirements (from Jira, GitHub, or GitLab) are covered by test cases and what the latest execution status is for each.
Overview
A traceability report is a point-in-time snapshot that answers three questions:
Which requirements have linked test cases? — These are covered.
Which requirements have no linked cases? — These are testing gaps.
What's the latest result for each linked case? — This shows where you're passing, failing, or haven't tested yet.
You can generate multiple versions of the same report over time to track how coverage and results evolve.
This is particularly valuable before releases — compare the current version to a previous one to confirm that new requirements have been picked up and regressions addressed.
Generating a report
Navigate to Traceability Reports and select Create a new report.
Give the report a title and choose from the supported integrations
Jira
GitHub
GitLab.
Select the external projects or repositories to include. You can select multiple.
Apply any integration-specific filters:
Jira — Filter by project and issue type.
GitHub — Filter by repository and milestone.
GitLab — Filter by project.
Generate the report. This may take a few moments depending on the number of requirements — you can leave the page and return later.
The report pulls requirements from your external tracker, not from Qase's requirements section.
Reading the report
Each report version displays:
Summary bar — Total requirements, linked count, and unlinked count per external project.
Linked / Unlinked tabs — Switch between requirements that have test cases attached and those that don't.
Requirement rows — Each row shows the requirement name, external ID (clickable link to the source), last-updated status and timestamp, and the number of linked test cases and defects.
Expand a requirement row to see:
Linked test cases with their latest run result, name, and case ID.
Associated defects with name, defect ID, and current status.
Filtering and searching
Use the search bar to find specific requirements by name, or apply filters to narrow by:
Requirement status
Test case result status
Defect status
This helps you focus on what matters — for example, filtering to show only requirements with failed test cases, so you can triage before a release.
Stale case detection
If a requirement was updated in the external tracker after its linked test case was last run, the report flags this.
You'll see an indicator suggesting you either re-run the case or mute it if no testing changes are needed. This prevents stale results from giving false confidence.
Versioning and tracking changes
Each report supports multiple versions, each generated at a different point in time. Use the version dropdown to switch between snapshots.
We recommend generating a new version:
Before and after a release to capture coverage delta.
After a sprint to measure testing progress.
Whenever significant requirements are added or changed in your external tracker.
The report dashboard shows all versions at a glance with their generation dates and linked/unlinked counts, making trends visible without opening each version individually.
Linking test cases to external requirements
For a requirement to appear as "linked" in the report, at least one test case must reference it. To create this link:
Open a test case in your repository.
Switch to the Properties tab.
Scroll to the external issue section and link the relevant requirement from your connected tracker.
This is the same mechanism used for linking defects to external issues — the traceability report simply reads these links at generation time.
Exporting
Select Export from the report view to download results:
CSV — Best for further analysis in spreadsheets or BI tools. Available with or without linked issue details.
PDF — Best for sharing with stakeholders. Available in landscape or portrait orientation.
Supported integrations
Traceability reports currently support:
Jira Cloud
Jira Server / Data Center
GitHub
GitLab
FAQ
Can I generate a report from Qase's internal requirements?
No. The traceability report is specifically designed to pull requirements from external issue trackers.
How often should I regenerate a report version?
There's no automatic schedule — generate a new version whenever you need a fresh snapshot. For most teams, once per sprint or before each release is sufficient.
Why do some requirements show as unlinked?
An unlinked requirement means no test case in your Qase project references that external issue. This could be intentional (the requirement doesn't need testing) or a gap you need to address. Filter for unlinked requirements to review them.