Trace Gap Which requirements have no verification?
One screen. One number. Answered from the issue links already in your Jira project — no import, no new data model, no migration.
Every requirements tool on the Marketplace can answer this. Most of them can only answer it after you have adopted their way of storing requirements. That is a project, and it is why the question usually goes unanswered until an audit forces it.
Trace Gap reads the issue types and issue links you already have. You tell it which types mean requirement and which mean verification, and it tells you which requirements have nothing pointing at them. First answer in about a minute.
What it does
- Counts requirements with no verification, and shows the coverage percentage.
- Lists exactly which ones, with key, summary, type and status.
- Exports the list as CSV for your audit record.
- Narrow what counts as verification by link type, or accept any link.
- Reads as you — it can never show an issue you could not already open.
What it deliberately does not do
No requirement authoring, no hierarchies, no baselines, no versioning, no document generation, no test execution. If you need a full requirements suite, buy one. This is the one report, done well — and priced as one report rather than as a suite.
Runs on Atlassian
The app runs entirely inside Atlassian's cloud and makes no network calls outside Atlassian. It requests read access only and cannot create, edit or delete anything in Jira. No issue data is stored. See security.
Not a compliance certification
Trace Gap produces evidence your own validated process can use. It does not certify your organisation against ISO 13485, IEC 62304, DO-178C, 21 CFR Part 11 or any other standard, and no such claim is made.