GitHub Enterprise Server sits inside your network. Atlassian's cloud cannot reach it — so a pull-based connector has nothing to pull.
Teams running GitHub Enterprise Server hit this the moment they try to see commits and pull requests on their Jira issues. The cloud-to-cloud integration assumes github.com; an on-premise GHES instance is unreachable from outside, and the integration quietly ends up empty.
The official connectors are pull-based: Atlassian's cloud has to reach your Git server's API to fetch commits and merge requests. That requires your server to be reachable from the public internet.
A self-hosted Git server behind a corporate firewall is, by design, not reachable from the outside. So the integration cannot complete — no matter how the tokens, scopes or webhooks are configured. It is not a misconfiguration on your side, and no support ticket will fix it. It is the direction of the connection.
Reverse the direction. BastionTrail is push-based: your Git server sends an outbound webhook to us when something happens. Corporate servers almost always have outbound access even when they have no inbound access at all — which is why this works where pull does not.
Once the events flow, BastionTrail assembles the chain auditors ask for: commit → merge request → who approved it → deployment to production. Exportable as CSV or a printable PDF, with Segregation-of-Duties detection (it flags a change approved by its own author) and a completeness score. The trail is hash-chained, so any edit breaks verification at the exact entry.
Install free on the Atlassian Marketplace
The connector is free with no user limit. Audit trail reports are the paid plan, with a 30-day trial. Security overview · Privacy
Honest status: GitHub Enterprise Server is implemented and covered by our test suite; GitLab self-managed is the provider we have proven end to end in a real environment. If you are a GHES team, tell us — setup is hands-on and the trial is on us.