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 test evidence 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. |
| Immutable commit SHA and bounded test files | Call the separate backend mapper | GitHub test artifact, revision, subjects, content hash, and provenance | Production connector resolvers do not call the mapper. |
| Test path or test declaration | Classify the source | Test evidence subject | Test paths and declarations are detected in mapper code, not the connector workflow. |
| Declared test-to-requirement relationship | Normalize a verifies link from test to requirement | Candidate trace link | Candidates are review-only and excluded from governed traversal. |
| Candidate link | Change its approval state through governance | Approved evidence link | Production version 6 has no approval resolver or visible approval control. |
| Approved or imported test and requirement nodes | Expand indexed graph neighbors from the test node | Test-to-requirement path under Forward impact | The current client never sends a selected startNodeId. |
How it works
- Open Git Connector as an administrator.
- Set Repository, Confluence space, and Allowed paths.
- Select Save connection.
- Select Scan by request for a report-only terminology check.
- Review Recent asynchronous jobs and Git terminology findings.
- Do not treat Add as draft as trace-link approval.
- Do not claim test-to-requirement trace evidence from this workflow.
Example
tests/payment.spec.ts exists at one fixed commit. The backend mapper can record its revision, hash, path, and a verifies requirement candidate. The connector never calls this mapper. No current control approves the candidate or starts workspace traversal from that test node.
What this does not mean
Production version 6 deploys a report-only GitHub connector. The separate mapper and indexed graph services are implemented and tested. They are not joined into one user workflow. End-to-end availability requires mapper invocation, candidate persistence, an approval control, and selected-node graph requests. Only approved or imported links qualify as governed evidence.
Related questions
Next step
Use Git Connector for terminology checks. Do not present its results as governed test-to-requirement trace evidence.
View on Atlassian Marketplace