On the Atlassian Marketplace. Free for teams up to 10 users.
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.
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.
| Repository | State | Detail |
|---|---|---|
| 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 |
Recorded on a real Jira site on 30 September 2026, on issue CHK-5. Nothing staged, times as measured.




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.
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.
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 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.
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.
It reaches your Jira site as it happens, over a signed webhook. Webhooks cost no GitHub API quota at all.
In branch names, commit messages and pull request titles, only for the projects that repository is attached to.
Straight into the native Development panel, so everything you already built on it keeps working.
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
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 size | Price |
|---|---|
| Up to 10 users | FreeThe whole app, not a trial |
| 11 to 100 users | $2.61per user per month |
| 101 to 250 users | $1.86per user per month |
Written here rather than discovered later, because that is the whole point of the product.
Short answers. The documentation has the long ones.
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.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 MarketplaceInstalls from Jira’s Apps menu. Questions first? support@linkwright.io