Linkwright permissions and sync statuses, explained
Before you install an app that reads your code, you should know exactly what it can do, and what the screens will tell you once it runs. This page lists both.
What the GitHub App can do, and why
The Linkwright for Jira GitHub App asks for these permissions, on the repositories you choose only (checked on 4 November 2026):
| Permission | Level | Why |
|---|---|---|
| Contents | read | Read commits and branches, to find the Jira issue keys in them |
| Pull requests | read | Read pull requests and their reviews |
| Deployments | read | Read deployment statuses, to mark commits as deployed |
| Metadata | read | Required by GitHub for every app (repository names) |
| Members | read | Check that the person who connects your GitHub organization to Jira is an owner of it |
| Repository webhooks | write | Create its own webhook when you attach a repository, and delete it when you detach it or uninstall (at uninstall, as many as Atlassian’s time limit allows: a site with many repositories may have to delete the rest by hand) |
It cannot change your code, your pull requests or your settings. GitHub’s webhook permission covers every webhook of a chosen repository, so it is the app’s code, not GitHub, that keeps it to its own: it only ever touches webhooks that point to your Jira site’s Linkwright address.
Why it asks for webhooks
Linkwright could have asked for read access only and checked GitHub every few minutes. It doesn’t, for two reasons:
- Speed. With a webhook, GitHub tells Linkwright about a push as it happens. Measured on 30 September 2026: a commit was linked to its issue 5.7 s after the push and sent to Jira at 7.2 s. Jira then took about a minute to show it in the Development panel; that part is Jira’s own indexing and is the same for every app. An app that checks every 5 minutes adds up to 5 minutes before that.
- GitHub’s rate limit. Webhooks cost nothing against it. Linkwright still re-reads every attached repository about every 35 minutes, to catch what a webhook missed on the default branch, in pull requests and in branch names, but it spends its quota on checking, not on waiting for news. Reviews, deployments and commits on other branches are not caught up by that re-read: they come by webhook, and Refresh catches up the commits of branches not seen yet.
The webhook is scoped: one per attached repository, signed with a secret unique to your Jira site, pointing to your Jira site’s own Linkwright address. Detach the repository from its last Jira project and the webhook is deleted.
Why it reads organization membership
Anyone who is a Jira administrator can open Linkwright’s settings. Without a check, a Jira admin who is only a regular member of a GitHub organization could connect that organization to Jira and expose its repositories there. Linkwright reads membership for one thing: to accept the connection only from an owner of the organization (or the account itself, for a personal account). If the Jira administrator isn’t an owner, they can send an owner a single-use invitation link, and the same check applies to the person who uses it.
What a project administrator can do
Connecting an organization is reserved for its owner. After that, attaching repositories is a Jira project setting: an administrator of a Jira project can attach any repository of a connected organization to that project, and its activity then appears on that project’s issues for anyone who can see them. Every project’s settings page lists the names of those repositories. A repository feeds only the projects it is attached to, but this choice isn’t limited to the repositories that administrator can see on GitHub. If that matters to you, limit who administers your Jira projects, or choose fewer repositories in the GitHub App.
What each sync status means
Every attached repository shows one status. A healthy status is never shown on a guess: each one comes from dated evidence. Next to it, the screens show the proof that sync happened: the last commit Jira accepted, and when (“Last delivered to Jira: commit abc1234, 3 min ago”), or “Nothing delivered to Jira yet” when nothing has been sent. Search and the Needs attention filter find the repositories that are not up to date.
| Status | What it means | What to do |
|---|---|---|
| Up to date | Read successfully less than 2 hours ago, with fewer than 3 failed reads in a row | Nothing |
| Out of date | The last successful read is more than 2 hours old | Click Refresh if you need it current now |
| Never checked | Attached, but not read successfully yet | Wait a few minutes, or click Refresh |
| Webhook down | The webhook could not be created (the screen gives the reason), or at least 3 commits appeared on the default branch with no webhook behind them: the re-read found them, and no delivery of any kind arrived in the 15 minutes that followed | On GitHub, open the repository’s Settings, then Webhooks: check that Linkwright’s webhook exists and is active, and read its recent deliveries. The status clears at the next delivery; if the webhook is gone, detach and re-attach the repository. Commits on the default branch keep arriving through the re-read, later; other activity waits for the webhook |
| Failing | 3 or more reads in a row failed, or Jira refused or lost what the repository sent; the screen shows the cause | Read the cause; contact support if it persists |
| Rate limited | GitHub’s request quota is used up for the current window | Nothing: it resumes on its own, and the screen says when |
| Not authorized | GitHub no longer gives access: the repository was removed from the GitHub App, renamed or deleted, or the connection was revoked | Add the repository back in the GitHub App’s settings, or detach it |
| Disabled | Sync turned off for this repository. Not used yet: this version has no switch for it, so the status does not appear | To stop syncing a repository, detach it |
Disabled cannot appear yet. It is listed because it is part of the app’s vocabulary, and saying so is more useful than leaving you to wonder.
How Webhook down avoids false alarms
A quiet repository receives no webhooks, so silence proves nothing. Linkwright only counts a contradiction: commits GitHub now shows that no delivery came with. These never count:
- commits from before you attached the repository, and everything its first read finds;
- commits a webhook arrives for within 15 minutes, or any commit when a delivery arrives meanwhile;
- commits older than a delivery that did arrive: an outage that has ended says nothing about now;
- the history after a force-push or a change of default branch.
Any delivery resets the count to zero, and so does detaching the repository from its last Jira project. Three limits: the status takes about an hour to appear, because commits are confirmed at the re-read after the one that found them (68 minutes in our test of 5 November 2026); only the default branch is checked, so a broken webhook goes unnoticed until commits land there; and one lost delivery of 3 or more commits shows the status until the next delivery arrives.
Already-linked commits stay on your issues whatever the status: a problem stops new activity from arriving, it does not erase what is there.
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
- GitHub for Atlassian is moving to Forge: what to check
- Limit which GitHub repositories each Jira project can link
- JQL for GitHub data in Jira
- 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