LinkwrightGitHub for Jira alternatives: how the options compare
If you are looking for another way to connect GitHub to Jira Cloud, these are the options on the Atlassian Marketplace, with their public numbers. Installs, ratings and prices were read from the public Marketplace API on 30 September 2026; the median rating of all Marketplace apps, measured on 12 September 2026, was 4.48.
| App | Publisher | Price | Installs | Rating | Reviews |
|---|---|---|---|---|---|
| GitHub for Atlassian | Atlassian | free | 137,087 | 3.34 | 508 |
| Git Integration for Jira | GitKraken | paid | 8,451 | 4.42 | 342 |
| GitHub Integration for Jira | Getint | paid | 555 | 3.88 | 18 |
| GitHub & Jira integration | Sieniar | paid | 367 | 4.38 | 18 |
| Linkwright for Jira | Linkwright | free up to 10 users | new | — | — |
Read the ratings with their dates
A rating is an average over a product’s whole life. GitKraken’s 4.42 rests largely on reviews from 2016 to 2020: of its 25 reviews written for the Cloud version from 2023 to 16 September 2026, 13 give one or two stars. For a Jira Cloud team, recent Cloud reviews say more than the headline number.
On the official connector, the complaint that comes back most often in the one- and two-star reviews is not a missing feature: it is that nothing gets linked, and nothing says why (about 37 % of the reviews with text we read in September 2026).
When the official app is the right choice
GitHub for Atlassian is free and installed on more Jira sites than every alternative combined. If your commits and pull requests show up reliably on your issues, keep it: nothing on this page is a reason to switch.
The alternatives exist for the teams for whom it does not hold: links that silently stop appearing, or a need the official app does not cover.
What Linkwright does differently
- It says how current its data is. Every repository shows its last webhook, its last successful read, and a plain state with the reason: Up to date, Out of date, Rate limited, Failing, Not authorized. A Refresh button rereads a repository on demand.
- It checks that Jira kept the links. Five minutes after sending, it rereads what Jira holds and repairs the links Jira dropped.
- Repositories are attached per Jira project. A repository shows up only in the projects it is attached to.
- Native Development panel. Commits, branches, pull requests and deployments appear where Jira
users already look, so JQL (
development[commits].all > 0) and Automation keep working. - Measured, not promised. On a real Jira Cloud site on 30 September 2026: a commit reached the issue in 5.7 s, and a single 500-commit push arrived whole.
- Built on Atlassian Forge: it runs on Atlassian’s infrastructure, and GitHub data is stored in the app’s Forge storage.
What Linkwright does not do yet
- GitHub.com only. No GitLab (self-hosted GitLab is planned), no Bitbucket, no Azure DevOps.
- Partial catch-up of older activity. When you attach a repository, recent commits on the default branch, recent pull requests and branches are linked; an older commit on another branch is not.
- No SOC 2 or ISO 27001. It is made for self-service teams of 20 to 200 people, not for enterprise procurement.
- It is new. No Marketplace reviews yet: judge it on a trial, and on the documentation, which lists every limit.
Questions, or a live demo on a real Jira site: saad@linkwright.io.