At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Requirement node | Select Forward impact | Connected governed artifacts | The requirement must exist in the deposited graph |
| Approved implementation link | Traverse to a document or code reference | Recorded implementation evidence | The link proves the recorded relation, not implementation quality |
| Approved verification link | Traverse to a test | Recorded validation evidence | Test execution status needs its own evidence |
| Deviation or release link | Preserve its typed relationship | Visible qualification or gate evidence | External approval remains outside the app |
How it works
- Open Enterprise evidence workspace.
- Search for the frozen requirement.
- Open its retained evidence.
- Select Forward impact.
- Review documents, code, tests, deviations, terms, and release gates.
- Open the evidence for each retained hop.
Example
A component requirement changes after a safety review. Forward impact shows the approved code reference, its validating test, a deviation, and a release gate. The team sees which governed artifacts need review. An unapproved suggested link stays outside this result until it is reviewed and accepted.
What this does not mean
The graph reports deposited relationships. It does not discover every dependency in source systems. A missing edge does not prove that no dependency exists. Teams must maintain complete approved links and visible coverage evidence.
Related questions
Next step
Use governed impact evidence before accepting a requirement change.
View on Atlassian Marketplace