Linkwright

Limit which GitHub repositories each Jira project can link

When a GitHub organization is connected to Jira Cloud, which repositories can link to which issues? With GitHub for Atlassian, Atlassian’s own tracker gives the answer: all of them, everywhere. Any issue key in any commit of any connected repository creates a link. That is fine for a single team. It is not fine when one GitHub organization serves several teams, clients or Jira sites that should not see each other’s code.

What Atlassian’s own tracker says about GitHub for Atlassian

A public request opened on Atlassian’s tracker on 21 October 2026, JRACLOUD-99914, describes the situation with GitHub for Atlassian:

The request asks for repository mapping per Jira site and per space. Its status is Gathering Interest. A related request from 22 October, JRACLOUD-99928, asks to control which integration’s data the Development panel shows.

The workarounds the ticket lists are blunt: move repositories into separate GitHub organizations, or remove the View Development Tools permission from a space, which hides the whole Development panel there.

Three boundaries, from the outside in

  1. GitHub: which repositories the GitHub App can read. Set on the GitHub side, per installation (“All repositories” or “Only select repositories”). Whatever the connector, nothing outside this list can reach Jira. Keep it as narrow as the teams that use Jira.
  2. Jira site: which installation the site is connected to. Decided by whoever connects it.
  3. Jira project: which repositories can link to its issues. This is the boundary teams usually mean, and the one JRACLOUD-99914 asks Atlassian for.

How Linkwright draws them

A repository links nothing until it is attached to a project. Each Jira project has a Git repositories page (Project settings → Apps). A repository creates links only on issues of the projects it is attached to; a commit in that repository that mentions an issue of another project is ignored there. Attaching a repository to two projects is allowed, and explicit.

Connecting an organization requires its owner role. A Jira administrator who is an owner connects a GitHub installation from the app’s admin page by signing in to GitHub once; one who isn’t can invite an owner with a single-use link. The app checks that this person is an owner of the organization (or the account itself), and checks again on the server when the connection is saved. Without that check, any organization member who is also a Jira admin could expose in Jira private repositories they cannot see themselves.

Each Jira site receives only its own repositories’ events. When a repository is attached, the app creates a webhook on that repository pointing to that Jira site, signed with a secret that belongs to that site. Two Jira sites connected to the same organization each get their own webhook, and only for the repositories attached on that site.

Detaching is reversible and clean. Detaching a repository from its last project removes its webhook and its entries in Jira’s Development panel within minutes. Disconnecting an installation detaches all of its repositories from every project.

What this does not do

Checklist

  1. In GitHub, set each installation to Only select repositories.
  2. In each Jira site, connect only the installations that site should see.
  3. In each Jira project, attach only the repositories its team works on, and use the Suggested list to find them: it shows repositories whose recent commits cite the project’s key.
  4. Check after a week: a commit that mentions another project’s key should not appear on that project’s issues.

Linkwright for Jira is free for up to 10 users: install it from the Atlassian Marketplace.