GitHub for Atlassian is moving to Forge: what to check
On this page
Atlassian is moving its free GitHub connector, GitHub for Atlassian (the app many teams still call “GitHub for Jira”), from the older Connect platform to Atlassian Forge. This page sums up what Atlassian says about it, and gives a short way to check, before and after, that your issues still carry their branches, commits and pull requests. Nothing here requires a particular connector.
What Atlassian says
From Atlassian’s migration page, GitHub for Atlassian is moving to Atlassian Forge (read on 10 October 2026):
- Who does it: Atlassian, in the background. Connected GitHub organizations, repositories and settings “will carry over automatically”, and there is “nothing you need to prepare”.
- When: final development in September–October 2026; production rollout and progressive validation in October; post-rollout verification in November–December.
- During the move: existing functionality “will continue to operate throughout the transition”. Atlassian says it will contact you and update the page if anything needs your attention.
On the Atlassian Marketplace, version 3.3.0 of GitHub for Atlassian (released 25 September 2026) is already listed as a Forge app.
Why check anyway
A platform move for more than 137,000 installations is rolled out progressively, so different sites switch at different times. Nobody — Atlassian included — can promise that every site sees exactly the same data before and after. Checking takes five minutes and turns “something looks off” into a number you can give to support.
Before: take a baseline (five minutes)
-
Count the issues that carry development data, per project. In Jira’s issue search, run:
project = ABC AND development[commits].all > 0and
project = ABC AND development[pullrequests].all > 0Write down both counts with the date. These fields are the ones Jira Cloud accepts; see JQL for GitHub data in Jira for the ones it refuses.
-
Pick two or three reference issues with recent activity — one with an open pull request, one with a merged one — and note what their Development panel shows (branches, commits, pull requests, deployments).
-
Note which repositories are connected. In Jira, the app’s configuration page: Settings → Apps → Manage apps → GitHub for Atlassian. On GitHub, the same list is under your organization’s Settings → GitHub Apps (or
github.com/organizations/<org>/settings/installations). -
List the Jira Automation rules that start from development events (branch created, commit created, pull request merged…). They are the first thing your team notices if events stop.
After: compare
- Run the same two JQL queries. The counts should not go down. They go up as new work is linked.
- Open the reference issues: the same branches, commits and pull requests should be there.
- Push a test commit whose message starts with an issue key (
ABC-123 check), and check that it appears on the issue within a few minutes. - On the configuration page, check that every organization is still connected and that no repository is missing.
- On GitHub, check that no permission update is waiting for an organization owner’s approval (organization Settings → GitHub Apps shows pending requests). A GitHub App whose new permissions are not approved keeps working with its old ones, which can leave some data out.
If something is missing
- Go through GitHub commits not showing in Jira: issue keys, repository access, backfill, permissions, a hidden Development field. Most cases are there.
- Re-run the backfill from the app’s configuration page, if it offers one.
- Contact Atlassian support with your baseline: “project ABC had N issues with commits on [date], it has M today”. A before/after number is the fastest way to get a case taken seriously.
- Atlassian’s public trackers: issues on atlassian/github-for-jira, and bug reports on jira.atlassian.com.
About this page
Written by the developer of Linkwright for Jira, another GitHub connector built on Forge, which shows for each repository whether its data is up to date and why not. The checks above work whatever connector you use. If you want a second connector to compare against, read 24 hours side by side with GitHub for Atlassian first — two connectors on the same repositories get in each other’s way — and see the Linkwright on the Atlassian Marketplace (free for up to 10 users).
More guides
- How to connect GitHub to Jira Cloud
- GitHub Issues vs Jira
- GitHub commits not showing in Jira
- GitHub for Jira backfill: restart it and check it
- Jira Smart Commits with GitHub: syntax and checks
- Limit which GitHub repositories each Jira project can link
- JQL for GitHub data in Jira
- Linkwright permissions and sync statuses, explained
- GitHub for Jira alternatives
- 24 hours side by side with GitHub for Atlassian
- GitHub organization not showing in Jira
- GitHub deployments not showing in Jira