nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Gitlab Jira integration Code and Deployments missing

Robert Morris_th7lj2

Dear community and support!

Can you help me, what could be the problem with integrating GitLab (Self-hosted) with Jira, that the issue displays commits, branches and pull requests, but in the code and deployment section it says that the integration needs to be completed (Finish connecting your code) and (You’re almost ready to view deployments in Jira) At the same time, the links also lead to the Gitlab login page.

Thank you in advance!

Accepted answers

All comments

Akash Singh_vujl0e

@Robert Morris Welcome to Atlassian Community!

Integrating Gitlab (Self-hosted) offering to Jira cloud would require you to install the Gitlab for Jira Cloud app using any of the two methods which are described in detailed here.

I would recommend going with installing the app in development mode as it is much easier than making your own marketplace listing of the app. This would enable Jira Development panel with Gitlab as the VCS source.

However, keep in mind for this to work your Gitlab instance has to be publicly available i.e. it should be behind a closed network which is only accessible via VPN or proxy which is one of the biggest challenges in integrating self-hosted Gitlab with Jira Cloud.

Note: Installing Gitlab for Jira Cloud directly from the marketplace won't work as it is intended for Gitlab.com (SaaS) only.

Dr_ Ankita Mehta-OpsHub_ Inc

Hi @Robert Morris

If you're seeing commits, branches, and pull requests in Jira but still getting messages like "Finish connecting your code" or "You’re almost ready to view deployments", it usually means the integration is working partially — specifically, the deployment and code event sync isn't complete.

Here are the most common causes:

Self-Hosted GitLab Needs Extra Setup: Jira’s native integration is optimized for GitLab Cloud. For self-managed instances, you typically need to manually configure web hooks, access tokens, and permissions to ensure all data flows correctly.
Auth or Access Issues: Redirects to the GitLab login page often mean Jira can’t authenticate or access the repository directly — especially common if the repo is private or if the token is missing or misconfigured.
Missing CI/CD Event Push: For deployments to show up in Jira, GitLab needs to send deployment data through its CI/CD pipeline. If these events aren't being sent to Jira, the deployment section stays empty.
Disconnected Entities: Even if commits are visible, Jira expects linked data — branches tied to issues, deployments tied to commits. If these links are missing, Jira flags the integration as incomplete.

If you're looking for a more seamless integration, OpsHub Integration Manager (OIM) (an Atlassian partner) offers full support for both GitLab Cloud and self-managed GitLab. It syncs issues, commits, branches, and deployment data — just connect the end systems and that's it.

Feel free to talk if you have any queries or want to request a demo.

Happy Integrating!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

integration

deployment

development

gitlab

code