At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Test evidence node | Link it with verifies or verified_by | Test-to-requirement, document, or code relationship | The endpoint pair must match the allowed relationship type |
| Deviation evidence node | Link it with deviates_from or deviation_evidence | Deviation connected to a requirement, document, code reference, or test | The link records evidence; it does not close the deviation |
| Approved or imported link | Add it to governed traversal | Forward and reverse trace hop | Candidate and rejected links do not count as evidence |
| Version and effective dates | Validate the evidence lifecycle | Time-bound relationship record | An end date must be later than its start date |
| Connector provenance | Retain source identity and recorded time | Evidence reference for the hop | Provenance does not prove source correctness |
| Broken or moved endpoint | Preserve the endpoint state | Visible trace issue | The app does not infer a replacement |
How it works
- Open Enterprise evidence workspace.
- Open Frozen meanings and revisions.
- Locate the requirement or implementation evidence.
- Select Open evidence.
- In Trace graph, select Forward impact to see tests and deviations downstream.
- Select Reverse provenance to follow them back to their governed basis.
- Open each Evidence reference. Review Coverage blockers before relying on the trace.
Example
A component requirement has an approved verified_by link to a safety test. That test has an approved deviation_evidence link to a recorded exception. Forward impact shows the requirement, test, and deviation as one governed chain. A candidate replacement test remains outside that chain until it is imported or approved.
What this does not mean
The trace records relationships. It does not execute tests. It does not approve deviations. It does not decide whether a test passed. It does not replace release approval or electronic signatures. Missing endpoints and traversal limits can make the visible result partial.
Related questions
Next step
Review the requirement-to-test-to-deviation chain before a release or audit handoff.
View on Atlassian Marketplace