Tagline: Commits, branches, pull requests, builds and file browsing from GitHub, GitHub Enterprise, GitLab, Bitbucket and Azure DevOps — on the issue, searchable in JQL, with smart commits. US$3/month up to 10 users, then US$0.90 per user.
Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Git Links for Jira. You need to be a Jira administrator.
PLAT-42 fix the parser.Git Links adds JQL fields, so you can ask things like gitCommits > 0 or gitPullRequestStatus = open in any Jira search or board filter.
For GitHub Enterprise, GitLab self-managed or Azure DevOps Server, add your own host under Customer-managed egress on the same settings page. You approve each host explicitly, one at a time, and can revoke it later.
Git Links for Jira puts the code behind a piece of work where the work is. Connect a repository once and every commit, branch and pull request that mentions the issue key shows up on the issue, with the files changed, the diff, the build status and how far the branch is ahead of main. Create a branch and open a pull request without leaving Jira. Browse any connected repository, at any branch, from a Repository Browser page inside Jira. Search all of it with JQL.
Five hosts, one app: GitHub, GitHub Enterprise Server, GitLab (SaaS and self-managed), Bitbucket Cloud and Azure DevOps (Services and Server). Webhooks index a push the second it lands; an hourly sync catches anything a webhook missed.
git switch command; and manual linking for the commit whose message forgot the key.{prefix}{key}-{summary}, plus {type} and {user}), are always valid per git check-ref-format, and never collide with an existing branch.#comment, #time, #transition and #label are always parsed and shown on the issue. They are only ever executed if a Jira or project administrator turns execution on for that project and allow-lists each command family. Every write carries an audit line naming the commit, the repository and the author the commit claims. Replays and retries cannot double-apply anything.gitCommits, gitBranches, gitPullRequests, gitOpenPullRequests, gitMergedPullRequests, gitDeclinedPullRequests, gitHasCommits, gitHasPullRequests, gitMerged, gitLastActivity, gitRepository, gitBranch. Example: project = PLAT AND status = Done AND gitHasCommits = "no" finds work marked done with no code behind it.| Host | Read | Create branch | Create pull request | Repository Browser | Builds | Webhook auth |
|---|---|---|---|---|---|---|
| GitHub.com | Yes | Yes | Yes | Yes | Actions + deployments | HMAC-SHA256 |
| GitHub Enterprise Server | Yes | Yes | Yes | Yes | Actions + deployments | HMAC-SHA256 |
| GitLab (SaaS + self-managed) | Yes | Yes | Yes (merge request) | Yes | Pipelines | Shared token |
| Bitbucket Cloud | Yes | Yes | Yes | Yes | Pipelines | HMAC-SHA256 |
| Azure DevOps (Services + Server) | Yes | Yes | Yes | Yes | Azure Pipelines | HTTP Basic |
Public repositories on GitHub, GitLab and Bitbucket work with no token at all — leave the token blank.
Every row is at least as good, and the price is lower in every band.
| Capability | Git Integration for Jira | Git Links for Jira |
|---|---|---|
| Commits on the issue (author, time, message) | Yes | Yes |
| Branches on the issue | Yes | Yes, with ahead/behind against the default branch |
| Pull requests with state | Open / merged / declined | Better — draft surfaced separately |
| Files changed per commit | Yes | Yes, on demand |
| Code diffs inside Jira | Yes | Yes, rendered inline, capped so a huge patch cannot break the page |
| Create branch from the issue | Yes | Yes, with a configurable name template, guaranteed-valid names and collision handling |
| Create pull request from the issue | Yes | Yes, via the provider API, with draft support |
| Repository Browser / repository browser | Yes | Yes — tree, branch switching, file contents with syntax highlighting |
| Smart commits (comment / time / transition) | Yes, site-wide | Better — opt-in per project, per command family, with an audit line, idempotent under replay, and always shown even when not executed |
| Project-level activity page | Yes | Yes, plus contributors and stale-pull-request flags |
| JQL search of git activity | Development-panel fields | Equivalent — twelve dedicated JQL fields (see below for the one Forge-imposed difference) |
| GitHub / GitHub Enterprise | Yes | Yes |
| GitLab SaaS / self-managed | Yes | Yes |
| Bitbucket Cloud | Yes | Yes |
| Azure DevOps | Yes | Yes |
| Repository-to-project permissions | Yes | Better — enforced on writes and indexing as well as reads |
| Webhooks for instant updates | Yes | Yes, signature-verified per connection, with replay protection |
| Scheduled / periodic reindex | Yes | Yes, hourly, deadline-aware and fair across repositories |
| Per-user or per-site tokens | Yes | Yes, plus token-less public repositories |
| Delegated (non-Jira-admin) administration | Yes | Yes, by group or account |
| Indexing failure alerts | Different — an https alert webhook (Slack, Teams, or anything that accepts JSON) plus in-product status. Forge apps cannot send email. | |
| Signals / Risk / Team views (Advanced edition) | Advanced tier only | Yes, included — contributors and stale-pull-request flags on the project page, at no extra tier |
| Small teams (up to 10) | US$10 / month flat | US$3 / month flat, every feature |
Two things the incumbent does that a Forge app cannot, stated plainly rather than promised:
development[...] JQL. Those are fed by the Jira Development Information API, which is available to Atlassian Connect apps that declare a jiraDevelopmentTool module. Forge has no equivalent module and cannot request those scopes. We ship the same capability as a first-class issue property with twelve JQL fields instead; the data lives on the issue, is readable by Automation and the REST API, and travels with the issue.One smaller, honest note: gitRepository and gitBranch match a whole repository or branch name, not a fragment of one — gitBranch ~ "release/2.0", not gitBranch ~ "release". That is how Jira indexes a text entity property.
| Users | Git Links for Jira | Git Integration for Jira (Standard, effective) |
|---|---|---|
| 1–10 | US$3 / month flat, every feature | US$10 / month flat |
| 11–100 | US$0.90 per user / month | ≈US$2.18–2.61 per user / month |
| 101–250 | US$0.70 per user / month | ≈US$1.24–1.55 per user / month |
| 251–1,000 | US$0.45 per user / month | ≈US$0.53–0.98 per user / month |
| 1,001+ | US$0.22 per user / month | ≈US$0.26–0.48 per user / month |
Annual is ten times the monthly rate, the Marketplace convention.
Why we can charge this. The feature matrix above is complete: there is no capability in the incumbent's Standard edition that we ask you to pay more for, and the contributor and stale-pull-request views they reserve for their Advanced edition are included here. What we do not carry is their cost base — no repository mirroring, no external indexing infrastructure, no 30,000-repository storage tier. Git Links runs entirely on Atlassian's Forge platform: the compute and the storage are Atlassian's, and the only thing we pay for beyond that is engineering. A small team gets the whole product for nothing; a large one pays well under half.
read:jira-work, write:jira-work, read:jira-user, storage:app. write:jira-work exists solely for smart-commit execution. Forge cannot request a scope conditionally, so it is always declared and every write is gated server-side on the per-project toggle, which defaults to off. With it off the app writes nothing to an issue except its own JQL summary property.api.github.com, gitlab.com, api.bitbucket.org and dev.azure.com are declared explicitly. A wildcard remains for the three features whose hostname is unknowable at manifest time — GitHub Enterprise Server, self-managed GitLab and Azure DevOps Server, plus the optional alert webhook — because Forge has no runtime domain registration. It is narrowed at runtime to a public DNS name whose last label is an alphabetic TLD (which rejects every inet_aton spelling of an IP literal, including 0x7f.1), never localhost or an internal suffix, https only, port 443 only, no embedded credentials, and redirects are never followed so a 30x cannot carry your token anywhere.401.git commit --author=…), and the app never treats it as proof of identity. The audit line says so explicitly.Email support with a one-business-day response. The documentation includes the issue-property JSON schema, so you can read the same data from Automation, ScriptRunner or your own tooling.