Git Links for Jira — every commit, branch and pull request on the issue, on five hosts, for a fraction of the price

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.

Getting started

1. Install

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.

2. Connect a repository

  1. Go to Settings (cog) → Apps → Git Links for Jira.
  2. Choose Connect repository and pick your host: GitHub, GitLab, Bitbucket or Azure DevOps.
  3. Paste a read-only access token for that host and the repository to watch, then choose Connect.
  4. The token is your Git host's credential, not an Atlassian one. Read-only scope is enough.

3. See commits on work items

  1. Reference a work item key in a commit message, branch name or pull request title, for example PLAT-42 fix the parser.
  2. Open that work item in Jira. The Git Links panel lists the commits, branches and pull requests that mention it.

4. Search on it

Git Links adds JQL fields, so you can ask things like gitCommits > 0 or gitPullRequestStatus = open in any Jira search or board filter.

5. Self-hosted Git

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.

If something looks wrong

Summary

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.

Highlights

Supported hosts

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.

Compared with Git Integration for Jira (GitKraken)

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 Email 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

What is not possible on Forge, and why

Two things the incumbent does that a Forge app cannot, stated plainly rather than promised:

  1. Populating Jira's built-in Development panel and its 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.
  2. Connecting to a git server over SSH, or to a host with a private or self-signed TLS certificate. Forge egress is HTTPS-only to declared domains, with a fixed trust store and no raw sockets or filesystem, so there is no way to speak the git protocol or clone a repository. Every supported host is reached through its HTTPS REST API. This also rules out Gerrit-over-SSH and generic self-hosted git servers with no REST API; AWS CodeCommit is closed to new customers by AWS and is not a live gap.

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.

Pricing

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.

Security and data handling

Support

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.