Documentation

What Trace Gap answers

One question: which requirements have no verification?

It answers it from the issue links that are already in your Jira project. You do not import anything, you do not adopt a new data model, and you do not re-enter your requirements somewhere else.

Setting it up

Open your Jira project and choose Trace Gap in the project menu.

1 · Requirement issue types. Pick the issue types that hold your requirements. Often Story, or a custom Requirement type.

2 · Verification issue types. Pick the types that count as evidence. Often Test, Test Case, or Task.

3 · Link types (optional). Leave this empty and any link counts as verification. Set it to narrow what counts — for example only is verified by if your team maintains that link type.

Press Find the gaps. That is the whole setup, and it is remembered per project.

Reading the result

You get a single number — how many requirements have no verification, and the percentage covered — followed by the list of the ones that do not.

Then export the list as CSV for your audit record.

The rules it applies

A requirement is covered when all of the following hold:

• its issue type is one of your requirement types, and
• it has at least one issue link, and
• that link points at an issue whose type is one of your verification types, and
• if you named link types, the link is one of them

Some deliberate details:

• Direction does not matter. An inward link counts the same as an outward one, so it does not matter which end of the relationship your team creates.
• Link type matching is case-insensitive, and you may name either the link type (Relates) or a direction phrase (is verified by).
• A link to the wrong kind of issue is still a gap. A requirement linked only to another requirement, or to a bug, is not verified.
• A link to an issue outside the project is not counted as evidence. If the report cannot see the target, it will not assume it verifies anything.

Permissions

Everything is read as the signed-in user. You can never see an issue through Trace Gap that you could not open in Jira. Colleagues with different project permissions may see different totals — that is correct behaviour, not a bug.

Limits

The report reads up to 5,000 requirements per project. Larger projects are truncated rather than timing out; if you have one, please write to us and tell us the size, because that number is a deliberate starting point and not a technical ceiling.

What it deliberately does not do

No requirement authoring. No requirement trees or hierarchies. No baselines or versioning. No document generation. No test execution. If you need a full requirements suite, buy one — this is the one report, done well.

It is 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.