One system hook, not a thousand webhooks
No per-repository setup. One instance-wide system hook covers every project you have and every project you add later. GitLab pushes out; nothing connects in to your instance.
SELF-MANAGED GITLAB CONNECTOR FOR JIRA
Your GitLab™ is behind a firewall. That has been the problem all along.
The usual approach needs your instance reachable from the outside. GitLab's own documentation for the official app is explicit about this: for a self-managed instance behind a firewall, you're told to stand up an internet-facing reverse proxy with a publicly trusted certificate, and open it to inbound connections. That's a security-review project, not a config change — and it still leaves your setup depending on a third party's uptime sitting between your two systems.
This app inverts it. Your GitLab pushes to Jira. Nothing reaches in, nothing needs to be exposed, and there is no per-repository configuration at all — a single GitLab system hook covers every project on the instance, including the ones created next week.
THE USUAL WAY
A public certificate, an open port and a proxy to maintain — a security review, not a config change.
THIS APP
One system hook, sending out. Nothing exposed, nothing new to operate, nothing sitting in between.
SEE IT WORK — 2:46
Nothing is loaded from YouTube until you press play. Playing loads the video from youtube-nocookie.com, a service of Google. English subtitles available; the voice-over is AI-generated. Or watch it on YouTube.
Commits that arrive before the issue exists are not lost
Push a commit referencing an issue key that hasn't been created yet and it is queued, not discarded. The moment the issue appears, the link is made — no re-push, no manual step, nothing for anyone to remember.
It tells you when something is wrong
The admin page shows ingest health, rejected entities and licence state. When something doesn't arrive, you can see that it didn't, and why — instead of discovering it weeks later in an empty panel.
Requires a self-managed or Dedicated GitLab instance where you have administrator access. GitLab.com is not supported — Atlassian's own GitLab for Jira app covers that case.
Pipelines, builds, deployments and tags are not included in this version. There is no historical backfill — linking starts from your next commit, and an active team's panel fills in within a day.
This app is built to be eligible for Atlassian's Runs on Atlassian programme. Your data stays on Atlassian's infrastructure — this app stores no customer data outside it.