Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Gitlab + Jira integration, merge request, build and deploy problems


I've successfully set up Gitlab integration from both the Market Place app and via Gitlab settings Jira integration. I've also set up Jira automation to transition tasks to different statuses.

I am having two problems:

  • Builds and Deploys are not showing up on Development section of the task even though commits, merge requests are there and branch is the name of the issue.
  • Merging a feature branch that contains multiple issues into the master branch doesn't transition the issues contained in the branch.


Builds and deploy problem:

Commit new branch named as issue ID with successful build.



Branches and commits show up on Jira task


But nothing shows up in build



Feature branch merge not transitioning issues problem:

Develop branch contains previous branches (issues), but I need to manually enter each issue ID into the description for Jira to pick it up. Since feature branch could have many issues, it's not feasible to have to manually do this every time.



2 answers

0 votes

It's probably about this issue here:

GitLab Deployments will only be logged from Merge Requests having the respective Jira Issue Key either in title, description or branch name.

We are facing the same issue atm as we are not deploying using MR but on change of our environment branches. Also we can't list up each and every Jira Issue Key when merging up. GitLab should rather detect keys based on commits.

Please give an upvote for the linked issue to increase its priority.

Hi Justin - did you ever get a resolution to the issue with builds not showing up? For myself, builds and deployments show up only on merge commits, yet I can't see anywhere in documentation that this shouldn't be updated for every commit against a branch, not just merge commits.

I'm trying to see whether the people configuring the application that we're building can see the status of their configuration as they commit to the feature branch, so they get early insight to any issues, not just when a merge is performed into the develop branch.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,098 views 34 44
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you