Linkwright

On the Atlassian Marketplace. Free for teams up to 10 users.

Your Jira should never lie about your code.

Linkwright puts GitHub branches, commits, pull requests, reviews and deployments on every Jira issue, and tells you, repository by repository, exactly how current that information is.

Measured on a real Jira site, not in tests

A demonstration issue was set up on 19 September 2026 and left untouched. Checked again on 22 and 30 September, it still carried its branch, its three commits, its merged pull request and its production deployment — and Jira’s own JQL still returned it.

~5 s
for a commit to appear on its issue
500
commits in one push, arriving whole
every
commit a deployment ships is marked, not just the last
Git repositories Project CHK
RepositoryStateDetail
acme/checkout-api Up to date Last check 40 s ago
acme/billing-worker Rate limited GitHub quota spent, resumes at 14:00
acme/legacy-portal Not authorized The GitHub App lost access to this repository
The most common complaint about Git connectors is that everything says “connected” while nothing gets linked. Here, a repository that falls behind says so, and says why.

One commit, from push to Jira.

Recorded on a real Jira site on 30 September 2026, on issue CHK-5. Nothing staged, times as measured.

  1. 20:14:08 CHK-5 shows one commit, from eleven days ago.
  2. +0 s A commit naming CHK-5 is pushed to GitHub.
  3. +5.7 s Linkwright links it to CHK-5. By +57 s, Jira’s own Development panel counts two commits.
  4. Then The commit and its message sit in Jira’s native panel, where JQL, boards and Automation see it.

The bridge between GitHub and Jira is the part everyone puts up with.

The complaint that comes back most often is not a missing feature. It is that every indicator says connected, nothing gets linked, and nothing says why.

I read 279 negative reviews of the two official connectors, one by one, before writing a line of code. Linkwright is built around that one sentence.

The cost is not really the developer’s. It is that issue status stops being a reliable picture of where the work stands — and you find out in the stand-up, or in front of a stakeholder.

Average rating on the Atlassian Marketplace, out of 5

GitHub for Atlassian 136,814 installs · 509 reviews
3.34
GitLab for Jira Cloud 32,499 installs · 342 reviews
2.75
Marketplace median 4.48
Read from the public Marketplace API on 12 September 2026.

What it does

Know what is current, before you report on it

Every repository shows its last webhook, its last full check, the last commit Jira accepted, and a plain state: Up to date, Out of date, Webhook down, Rate limited, Failing or Not authorized, with the reason. One click re-reads it from GitHub.

The Git repositories screen, showing each repository with its sync state and the time of its last successful check.

Your boards, JQL and Automation keep working

Commits, branches, pull requests with approvals and deployments land in Jira’s native Development panel, so boards, JQL and Automation keep working as they do with Atlassian’s own integration. A deployment is linked to every commit it ships, not only to the last one.

A Jira issue whose Development panel is filled by Linkwright: branches, commits, pull requests and a production deployment.

Repositories stay in the projects you choose

A repository only links to issues of the Jira projects it is attached to. Connecting a GitHub organization requires one of its owners. After that, Jira decides: a project administrator can attach any repository of that organization, and whoever can see the project’s issues sees its activity.

Connecting a GitHub organization from Jira administration; only a GitHub owner of that organization can connect it.

Webhooks first. Polling only to catch what they missed.

A team with three thousand repositories gets about four GitHub API requests per repository per hour. Polling does not fit in that budget, which is exactly why the connectors that rely on it fall behind.

  1. GitHub pushes the event

    It reaches your Jira site as it happens, over a signed webhook. Webhooks cost no GitHub API quota at all.

  2. Issue keys are matched

    In branch names, commit messages and pull request titles, only for the projects that repository is attached to.

  3. Jira is updated

    Straight into the native Development panel, so everything you already built on it keeps working.

  4. A periodic check catches most of the rest

    Unchanged data costs little to re-check. What a webhook missed on the default branch, in pull requests or in branch names is picked up within about 35 minutes.

Linkwright runs entirely on Atlassian Forge. Your data stays in your own Jira site’s storage, there is no server of mine anywhere, and no Jira data is ever sent to GitHub. Read the security policy

Free for small teams.

Per user, per month, billed through the Atlassian Marketplace. Above ten users, the price matches the leading paid connector. Approved by Atlassian with the listing on 2 November 2026.

Team sizePrice
Up to 10 usersFreeThe whole app, not a trial
11 to 100 users$2.61per user per month
101 to 250 users$1.86per user per month

What it does not do yet

Written here rather than discovered later, because that is the whole point of the product.

GitHub.com only
GitLab, including self-hosted GitLab, is planned for a later version.
Bounded catch-up of older activity
When you attach a repository, recent commits on the default branch, recent pull requests and branches are linked, plus the commits of up to 20 branches not seen yet. Each Refresh catches up 20 more.
Reviews and deployments come by webhook only
The periodic check does not back-fill them, nor commits on branches other than the default one: Refresh catches those up.
No certification
No SOC 2, no ISO 27001. It is made for self-service teams of 20 to 200 people, not for enterprise procurement.

See the full list in the documentation

Questions teams ask first

Short answers. The documentation has the long ones.

Which Git hosts does it support?
GitHub.com, through a GitHub App you install on your account or organization. GitHub Enterprise Server and GitLab are not supported in this version.
Do Smart Commits, JQL and Automation still work?
JQL and Automation, yes: Linkwright fills Jira’s own Development panel, so development[commits] in JQL, board badges and automatic transitions behave as they do with Atlassian’s integration. Smart Commits (#comment, #time, #transition in a commit message), yes since 2 November 2026, for commits you write and push yourself, on issues of the projects the repository is attached to: see the Smart Commits guide.
What leaves our Jira site?
No Jira data is sent to GitHub, only what it takes to read your repositories and, for each webhook, your site’s address and secret. Linkwright reads from GitHub and writes to your Jira site, and runs entirely on Atlassian Forge: there is no server of mine in between. Details in the security policy.
Who can see which repositories?
A repository feeds only the Jira projects it is attached to, and only an owner of the GitHub organization can connect it to your site. Once connected, access follows Jira, not GitHub: anyone who can see an issue sees the activity linked to it, even from a private repository they cannot open on GitHub. Every permission the GitHub App asks for, and why.
What happens when a link breaks?
The repository’s state changes to Webhook down, Rate limited, Failing or Not authorized, with the reason and the time of the last success. Refresh re-reads it from GitHub. What each state means.
Who is behind it, and how fast is support?
One independent developer, registered in France. First response within two business days, on the support portal or at support@linkwright.io.

Try it on your Jira today, free.

Linkwright is on the Atlassian Marketplace: it installs on your Jira site in two minutes, from Jira’s own Apps menu. Free for teams up to 10 users, with a free trial above that.

You write to the person who wrote the code: first answer within two business days, usually the same day. Prefer to see it first? I can show it to you live, on a real Jira site, in fifteen minutes.

Saad Lagzouli, who builds Linkwright

Get it on the Atlassian Marketplace

Installs from Jira’s Apps menu. Questions first? support@linkwright.io