Skip to:

Marketplace

Self-Managed Connector for Jira (GitLab™ Compatible)

works with Jira Cloud

OVERALL RATINGS

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appCommits and merge requests from a self-hosted instance behind your firewall, in Jira. One system hook covers every project

watch Self-Managed Connector for Jira (GitLab™ Compatible) video

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.

Commits that arrive before the issue aren't 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.

More details

This app is not affiliated, endorsed, sponsored, or approved with or by GitLab Inc. GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions.

Requires: a self-managed or Dedicated GitLab instance where you have administrator access (system hooks are instance-wide, so they are an admin feature). GitLab.com is not supported — the official app covers that case.

What this does not do (yet): pipelines, builds, deployments and tags are not included in this version. There is no historical backfill — linking starts from your next commit.

Branches and merge requests are not queued: if the issue does not exist yet, the app reports it on the administration page instead of retrying. Push again and it links.

When you don’t need this app: if your GitLab instance is reachable from the internet, or you can put a reverse proxy in front of it and allowlist a vendor’s IP ranges, other integrations will serve you well and some of them do more than this one.

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Self-Managed Connector for Jira (GitLab™ Compatible) integrates with your Atlassian app

Version information

Version 3.0.0•for Jira Cloud

Release date
Oct 12th 2026
Summary
Explicit Jira administrator check on the configuration page
Details

This version adds one permission, View permissions (read:permission:jira). It is used for one thing only: every action on the app’s configuration page now checks, on the app’s side, that the person using it is a Jira administrator before anything is shown or changed. If that check cannot be completed, nothing is shown or changed. The app reads no issues, projects or user profiles with this permission.

Because the permissions change, existing sites are not upgraded automatically. A Jira administrator approves the update under Apps, Manage apps. Until then the previous version keeps working as before. New installations get this version directly.

Nothing changes in what the app sends to Jira or in the GitLab system hook. No reconfiguration is needed after the upgrade.

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow