At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Governed term node | Select Forward impact | Connected governed nodes and links | The term must exist in the deposited graph |
| Imported or approved link | Add it to the impact index | Queryable evidence relationship | Candidate and rejected links are excluded |
| Broken or moved endpoint | Preserve its endpoint state | Visible issue in the result | The app does not repair the source |
| Hop and result bounds | Run a bounded graph walk | Truncation state when a bound is reached | Up to 20 hops and 1,000 results per request |
How it works
- Open Enterprise evidence workspace.
- Search for the frozen term.
- Open its retained evidence.
- Select Forward impact.
- Review every returned artifact and endpoint issue.
- Open the evidence attached to each retained hop.
Example
An approved term changes before a controlled release. The governance team opens the prior baseline and selects Forward impact. The graph shows an approved requirement link, two document links, a code reference, and a test. A moved endpoint remains visible. The team uses that result to scope review and external reissue work.
What this does not mean
Impact lookup reports only relationships present as imported or approved evidence. It does not infer every real-world dependency. A missing result can mean no governed link was deposited. It does not prove that an artifact is unaffected.
Related questions
Next step
Review governed impact before changing an approved term used by controlled artifacts.
View on Atlassian Marketplace