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

Add tag-list from gitlab branches or tags

Hi there,

I am working on Jira-Gitlab automation and one of the tasks is to add some drop-down list from gitlab tags or branches. I can define some tag and pass it via webhook to run in gitlab-ci.yml but I want to have a list of available gitlab tags in the sidebar of the issue after it's creation. 

How this can be done? Preferably without any paid plugins. But I will consider all variants. 


2 answers

Yes, thank you very much for the reply @Andy Heinzer . Generally the last paragraph is what we use now. When user points in issue the tag or the branch for specific repository and through automation and webhook it is being passed to gitlab pipeline. 

As for the market place while I was investigating it, it is little bit different apps and have not found what was looking for. 

So something mentioned in the 2nd paragraph should be done... On ticket creation some webhook to gitlab should be passed and list of available tags or branches should be returned. That is where I stuck. Not really sure if this is possible to do in my case. 

0 votes
Andy Heinzer Atlassian Team Jun 13, 2022


I understand you want to be able to see the gitlab tags as field options within Jira.  I'm not exactly sure how to best do this.  But I did come across a Marketplace app that appears to provide these kinds of git tags within Jira.  Check out Git Integration for Jira.  There might be other solutions in marketplace as well.

It might be possible to get some of these tags within Jira without using that specific app.  I was thinking that you might be able to use automation in Jira in order to either receive a webhook with this info, or to make a webhook (web request) to gitlab to obtain this info.  The problem with this approach is that Jira custom fields like a select list cannot simply have their potential values different for each issue in a project.  Instead an administrator is expected to setup the potential values in advance for a field, and then on an issue level, a user chooses what value is applied to that issue.

You might be able to circumvent this to some degree by using a different field type.  A custom field type such as labels in Jira will allow the end user to input new values into an array type field.  But this is not technically a drop-down field. So perhaps this method is not what you are looking for here.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Coming Soon: Insight Changing to Assets

The 2020 acquisition of Mindville added powerful asset and configuration management capabilities to Jira Service Management in the form of Insight. Following the completion of that integration, custo...

338 views 3 11
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