Tracer / Demo
A delivery effort with 11 hidden gaps
This synthetic Jira export describes a small product: 6 requirements, 3 test cases, 3 defects. On the surface it looks like an ordinary backlog. It carries 11 gaps an auditor would find: 4 requirements with no test at all, 1 test attached to nothing, and 6 records missing the fields a status computation needs. Everything below was computed from that export when this page was served — open any finding to see the record behind it.
Why Tracer refused
Status: Not computable
Status withheld: 6 required fields are missing. A status computed over missing fields would be a guess, and guessed values are never emitted. Fill each blocking field in its source system and recompute.
No substitute number was produced in its place — no score, no grade, no estimate. Tracer names the
6 record and field pairs that block the computation and stops there.
Fill them in the source system and the status computes on the next run.
| Record | Missing field | Check |
| DEMO-2 | priority | src/status.ts#required_field |
| DEMO-3 | priority | src/status.ts#required_field |
| DEMO-5 | last_result | src/status.ts#required_field |
| DEMO-6 | last_result | src/status.ts#required_field |
| DEMO-7 | last_result | src/status.ts#required_field |
| DEMO-9 | severity | src/status.ts#required_field |
Provenance for this refusal
| source_system | demo:jira-export.json |
| source_records | 6 (listed above) |
| extraction_logic | src/status.ts#required_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
Every finding, with the record behind it
Each finding names a rule, a record, and a repair. Open one to see its provenance: the system the record came from, its identifier, the check that produced the finding, and when the data was read.
missing_field DEMO-2 — Requirement DEMO-2 has no priority.
| Record | DEMO-2 |
| Field | priority |
| Rule | missing_field |
| Finding | Requirement DEMO-2 has no priority. |
| Suggestion | Set a priority so gap and risk views can rank this requirement. |
| source_system | demo:jira-export.json |
| source_id | DEMO-2 |
| extraction_logic | src/linter.ts#missing_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
missing_field DEMO-3 — Requirement DEMO-3 has no priority.
| Record | DEMO-3 |
| Field | priority |
| Rule | missing_field |
| Finding | Requirement DEMO-3 has no priority. |
| Suggestion | Set a priority so gap and risk views can rank this requirement. |
| source_system | demo:jira-export.json |
| source_id | DEMO-3 |
| extraction_logic | src/linter.ts#missing_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
missing_field DEMO-5 — Test case DEMO-5 has no recorded last result.
| Record | DEMO-5 |
| Field | last_result |
| Rule | missing_field |
| Finding | Test case DEMO-5 has no recorded last result. |
| Suggestion | Record the outcome of the most recent run, or mark the test as never executed. |
| source_system | demo:jira-export.json |
| source_id | DEMO-5 |
| extraction_logic | src/linter.ts#missing_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
missing_field DEMO-6 — Test case DEMO-6 has no recorded last result.
| Record | DEMO-6 |
| Field | last_result |
| Rule | missing_field |
| Finding | Test case DEMO-6 has no recorded last result. |
| Suggestion | Record the outcome of the most recent run, or mark the test as never executed. |
| source_system | demo:jira-export.json |
| source_id | DEMO-6 |
| extraction_logic | src/linter.ts#missing_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
missing_field DEMO-7 — Test case DEMO-7 has no recorded last result.
| Record | DEMO-7 |
| Field | last_result |
| Rule | missing_field |
| Finding | Test case DEMO-7 has no recorded last result. |
| Suggestion | Record the outcome of the most recent run, or mark the test as never executed. |
| source_system | demo:jira-export.json |
| source_id | DEMO-7 |
| extraction_logic | src/linter.ts#missing_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
missing_field DEMO-9 — Defect DEMO-9 has no severity.
| Record | DEMO-9 |
| Field | severity |
| Rule | missing_field |
| Finding | Defect DEMO-9 has no severity. |
| Suggestion | Set a severity so triage and exposure views can weigh this defect. |
| source_system | demo:jira-export.json |
| source_id | DEMO-9 |
| extraction_logic | src/linter.ts#missing_field |
| query_timestamp | 2026-09-11T00:49:48.612Z |
orphaned_test DEMO-6 — Test case DEMO-6 is linked to no requirement.
| Record | DEMO-6 |
| Rule | orphaned_test |
| Finding | Test case DEMO-6 is linked to no requirement. |
| Suggestion | Link the test case to the requirement it verifies, or record why it is intentionally standalone. |
| source_system | demo:jira-export.json |
| source_id | DEMO-6 |
| extraction_logic | src/linter.ts#orphaned_test |
| query_timestamp | 2026-09-11T00:49:48.612Z |
untested_requirement DEMO-2 — Requirement DEMO-2 has no linked test case.
| Record | DEMO-2 |
| Rule | untested_requirement |
| Finding | Requirement DEMO-2 has no linked test case. |
| Suggestion | Add at least one test case tracing to this requirement; until then it is an untested area. |
| source_system | demo:jira-export.json |
| source_id | DEMO-2 |
| extraction_logic | src/linter.ts#untested_requirement |
| query_timestamp | 2026-09-11T00:49:48.612Z |
untested_requirement DEMO-3 — Requirement DEMO-3 has no linked test case.
| Record | DEMO-3 |
| Rule | untested_requirement |
| Finding | Requirement DEMO-3 has no linked test case. |
| Suggestion | Add at least one test case tracing to this requirement; until then it is an untested area. |
| source_system | demo:jira-export.json |
| source_id | DEMO-3 |
| extraction_logic | src/linter.ts#untested_requirement |
| query_timestamp | 2026-09-11T00:49:48.612Z |
untested_requirement DEMO-13 — Requirement DEMO-13 has no linked test case.
| Record | DEMO-13 |
| Rule | untested_requirement |
| Finding | Requirement DEMO-13 has no linked test case. |
| Suggestion | Add at least one test case tracing to this requirement; until then it is an untested area. |
| source_system | demo:jira-export.json |
| source_id | DEMO-13 |
| extraction_logic | src/linter.ts#untested_requirement |
| query_timestamp | 2026-09-11T00:49:48.612Z |
untested_requirement DEMO-14 — Requirement DEMO-14 has no linked test case.
| Record | DEMO-14 |
| Rule | untested_requirement |
| Finding | Requirement DEMO-14 has no linked test case. |
| Suggestion | Add at least one test case tracing to this requirement; until then it is an untested area. |
| source_system | demo:jira-export.json |
| source_id | DEMO-14 |
| extraction_logic | src/linter.ts#untested_requirement |
| query_timestamp | 2026-09-11T00:49:48.612Z |
Records Tracer skipped
2 issues in the export carry issue types
the connector does not map to a requirement, test case, or defect. They are counted and disclosed
here rather than dropped, because a record Tracer did not read is a limit on the finding list above.
| Issue type | Skipped |
| Epic | 1 |
| Task | 1 |
Issue types map case-insensitively: Story and Requirement become requirements, Test becomes test cases, Bug and Defect become defects. Other issue types produce no record and are counted per type; this export skipped 2 issues. Requirement dependencies come from Blocks and Depends links, outward direction only, and only when the target is itself a mapped requirement; inward links and links to unmapped issues are ignored. A test case's requirement is the first Tests or Relates link target in link order, outward key preferred over inward within a link; link type names also match case-insensitively. The search response carries no execution results, so no test case gets a last result — a result that was never recorded is never invented, and the gates report each test as missing it. The search response carries no area field and no declared defect-to-requirement link, so area and defect requirement ids stay empty and read as missing. Product identity derives from the project prefix of the first issue key; this export identifies as DEMO.
Run it yourself
Run the demo scanLoads this same export into the scanner and analyzes it — nothing to paste
Sample audit evidence packWhat the full assessment delivers, every claim carrying its provenance
Model your own business caseYou supply every assumption, the arithmetic is printed on the page, and the result is a modeled scenario
The demo export is fictional and ships with this site —
inspect it yourself. Your own scans work the same way: no credentials, nothing stored.
Source: demo:jira-export.json · as of 2026-09-11T00:49:48.612Z · Tracer fc931641