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; } } }

Automate Transition of Jira Issue based on GitLab code merge on different branches

Junaid Shahzad

Hi,

I have created a workflow like below

- To-Do

- Progress

- Deployed-QA

- Deployed-Production

what i want if

I do a merge in GitLab repository in QA branch its should change/transit the status of ticket/issue to Deployed-QA.

I do a merge in GitLab repository in Production branch its should change/transit the status of ticket/issue to Deployed-Production.

Thanks in Advance if anyone can help to setup this type of trigger or config in jira and GitLab. I am using Jira managed cloud.

Accepted answers

Stefan Salzl

Hi @Junaid Shahzad and welcome to the comunity

first question upfront:
Did you already integrate your gitlab into jira so that development info can be shown in jira issues?

see following links regarding this topic and how to configure:
https://docs.gitlab.com/ee/integration/jira/development_panel.html

https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/

Best
Stefan

All comments

Stefan Salzl

Hi @Junaid Shahzad and welcome to the comunity

first question upfront:
Did you already integrate your gitlab into jira so that development info can be shown in jira issues?

see following links regarding this topic and how to configure:
https://docs.gitlab.com/ee/integration/jira/development_panel.html

https://support.atlassian.com/jira-software-cloud/docs/view-development-information-for-an-issue/

Best
Stefan

Junaid Shahzad

Thanks for reply, yes i already integrated the Jira when i reference the issue number during any push /merge i can see comments under tickets related that merge/push. below the link i followed to integrate.

https://docs.gitlab.com/ee/integration/jira/configure.html

Stefan Salzl

How does your branch structure/flow looks like? are your using a starndard flow (like gitFlow, trunkbased, githubFlow)?

Is your "production" your baseline (like your main-branch)? or does production gets branched from main? and then dev from production? and where is QA branched away from?

Sorry for that load of questions. The better we are aware of the situation the better we could strive for a solution.

Best
Stefan

Junaid Shahzad

branch structure is

qa (for qa env all development work done here after feature test we merge it to pre-prod branch)

pre-prod (replica of production but not production it use to deploy on pre-prod env after testing its code merged to master)

master (its use to deploy on production env and its get merge from pre-prod no direct push allowed )

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

transition

automation

gitlab