Linkwright

GitHub organization not showing in Jira: why, and how to connect it

You installed GitHub for Atlassian, your GitHub admin says access is granted, and GitHub even shows “Atlassian is installed” on the organization. Yet the app’s configuration page in Jira doesn’t list that organization, and its developers’ commits don’t appear on Jira issues.

“Installed” and “connected” are two different states. This page sums up what Atlassian documents about the second one, read on 9 November 2026, and what to check in order.

Installed on GitHub is not connected to Jira

The GitHub App can be installed on an organization without that organization being connected to your Jira site. The Jira configuration page lists connections, so reinstalling the app does not create the missing one. It does restart your history from the default six months: see how the backfill works.

1. Check who is clicking Connect

Atlassian’s rule: “You’ll have the Connect button only if you’re the owner of the GitHub organization.” Being a Jira site administrator isn’t enough, and neither is a lesser role on GitHub.

Atlassian expects this to be two people in some teams: a Jira site admin installs the app, and a GitHub organization owner connects the organization.

The documented route:

  1. The Jira admin starts connecting an organization and chooses Send them a link and ask them to connect.
  2. They copy the message and URL from the Send a link to an organization owner dialog and send them to the owner.
  3. The owner uses the link to sign in and connect the organization to Jira.

Atlassian’s support article for this case describes an owner who has no access to Jira. It also has the owner go to Settings > Third-party Access > OAuth application policy on GitHub, grant Atlassian Cloud access, and install the pending Jira app.

The pages don’t say whether the owner needs an Atlassian account to follow the link. If the owner is blocked at that step, note the exact message they see: it is what support will ask for.

3. Check the organization’s IP allow list

Atlassian warns that an IP allow list can cause problems with the app, and that “GitHub blocks some requests to the API even if the correct IP addresses are listed in the allow list”. An organization admin can check it on GitHub:

  1. Open the organization’s Settings tab, then Organization security in the sidebar.
  2. Scroll to the IP allow list section.
  3. Select Enable IP allow list configuration for installed GitHub apps, then Save.

If requests are still blocked, Atlassian’s fallback is to add the addresses by hand with +Add.

In a public report from 2022 (issue 1288 of the app’s repository), the logs showed the app could not determine the user’s admin status in the missing organization, with GitHub answering 403.

4. Try a clean sign-in

In that same 2022 report, IP allow listing was off. The organization appeared after the reporter cleared their cookies for github.atlassian.com and signed in again. It is one report and an old one, but it takes a minute to try.

5. Check which GitHub you are on

These steps cover GitHub Cloud and GitHub Enterprise Cloud. GitHub Enterprise Server has its own setup page, which asks for your server’s URL.

After the organization is connected

Connecting it gives you links from then on, plus an initial import of history. To confirm it worked, pick an issue whose key appears in a recent commit of that organization and open its Development panel. If it stays empty, see GitHub commits not showing in Jira.

The same rule in Linkwright

We build Linkwright, another GitHub integration for Jira, so here is how it compares on this one point: it has the same owner rule, for the same reason (a Jira admin who isn’t an owner shouldn’t be able to show an organization’s private repositories in Jira). If the Jira admin isn’t an owner, they can send one a single-use invitation link. One difference from Atlassian’s documented case: the owner needs access to Jira on your site, because the link opens a page inside Jira. When someone can’t connect an organization, the screen says why instead of leaving it out of a list.