Compliance Glossary for Confluence

What is forward term traceability?

Forward term traceability starts from an approved term node and follows governed links downstream. Choose the node in Start node, select Show trace graph, then Forward impact. The graph can show linked requirements, documents, code references, tests, and deviations. Only approved or imported links count. Coverage blockers show when results are partial.

Last verified against production v6 · 24 October 2026

At a glance

InputActionOutputLimit
Approved term trace nodeChoose it in Start node and select Show trace graphForward and reverse hops from the termTerm nodes come from Declare trace node and need another administrator's approval
Approved or imported linkFollow it downstreamRequirement, document, code reference, test, or deviation hopRelation and endpoint types must match the trace contract
Frozen term usageSelect Show impact in Frozen meanings and revisionsArtifacts where the frozen term was observedUsage does not create trace links
Candidate or rejected linkSkip it during traversalNot part of the resultReview it in Trace links awaiting approval
Broken, moved, or missing endpointReport it instead of expanding itEntry under Coverage blockersThe app does not infer a replacement link
Large or cyclic graphApply hop and result boundsBounded resultWorkspace default 5 hops and 200 links

How it works

  1. Open Terminology Baseline.
  2. Scroll to Enterprise evidence workspace.
  3. In Trace graph, choose the approved term node in Start node.
  4. Select Show trace graph.
  5. Select Forward impact.
  6. Review each hop and its Evidence reference.
  7. Check Coverage blockers before relying on the result.

Example

An approved term node has governed used_by links to a policy document and a code reference. Forward impact shows both hops. A suggested test link is still a candidate, so it does not appear. If an endpoint is missing, Coverage blockers lists it and the result is partial.

What this does not mean

Forward traceability shows recorded links only. It does not discover every semantic reference in content. It does not promote candidate links. It does not prove that a relationship is complete or correct. The Start node picker lists declared nodes, not frozen term records. Hop and result limits can produce a partial view.

Related questions

Next step

Run Forward impact from the approved term node before approving a terminology change.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 24 October 2026.