At a glance
| Input | Current action | Output | Boundary |
|---|---|---|---|
| Approved GitHub repository | Configure Repository, Confluence space, and Allowed paths | Report-only terminology scan scope | The connector does not create code nodes or requirement links. |
| Connector scan | Select Scan by request | Recent asynchronous jobs and Git terminology findings | Add as draft creates a glossary draft, not a trace link. |
| GitHub file or commit URL | Declare trace node with type code_reference | Candidate code node with your reference | The app does not fetch, capture, or hash the revision. |
| Code node and requirement node | Declare trace link with relation implements and an Evidence reference | Candidate trace link | Candidates are excluded from traversal. |
| Candidate node or link | Another administrator selects Approve with a Review reason | Governed node or link | Four-eyes: the declarer cannot approve it. |
| Approved start node | Choose it in Start node, select Show trace graph | Code and requirement hops | Requirement is upstream of code. |
| Missing endpoint or truncated graph | Review Coverage blockers | Explicit incomplete-coverage reason | Partial paths are not complete trace coverage. |
How it works
- Open Terminology Baseline and scroll to Enterprise evidence workspace.
- Use Declare trace node: type code_reference, a title, the GitHub URL in External reference or URL, and a reason.
- Use Declare trace link: the code node as From node, the requirement as To node, relation implements.
- Ask another administrator to approve in Trace nodes awaiting approval and Trace links awaiting approval.
- In Trace graph, choose the requirement in Start node and select Show trace graph.
- Select Forward impact to see the code, or start from the code node and select Reverse provenance.
- Check Coverage blockers before relying on the result.
Example
A payment service contains authorizePayment at a fixed commit. An administrator declares a code_reference node with the commit permalink and an implements link to the authorization requirement. A second administrator approves both. Forward impact from the requirement now lists the code hop.
What this does not mean
Production runs a report-only GitHub connector, with scans by request. Backend code that maps GitHub revisions into trace evidence exists, but nothing in production calls it. The code node stores the URL you entered, not a hashed revision. Only approved or imported links qualify as governed evidence.
Related questions
Next step
Declare code nodes with exact commit permalinks and have a second administrator approve them before relying on the trace.
View on Atlassian Marketplace