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

Transition issue when pull request is merged on a specific branch in Github

grant.stevens@thingtech.com

I'm trying to figure out how to transition an issue when a developer merges a pull request that contains a Jira-linked commit. I'm trying to automate a specific part of our workflow to eliminate the need for developers to manually transition a story.

I basically need a conditional trigger on a workflow transition so I can say something like "when a pull request is merged to master that contains a related commit, transition this story".

I know that we could probably achieve this with smart commits, but that requires engineers to remember to add the proper hashtag to their commit messages for the merge branch. I want to eliminate as much human interaction as possible, so smart commits don't fit the bill.

Is there a way to script this somehow? I'm still a bit new to Jira administration, so I'm familiar with the possibilities.

Thanks!

Accepted answers

Julio Kenji Bando

Hello!

I was looking for the same here then I found that it's already available in automation rules:

Jira Automation Rules

All comments

Daniel Eads

Hey Grant,

Smart commits were my first thought when reading the title of your question. However, I think for your case you want Workflow Triggers instead. These are supported with Jira Cloud and Github (both Cloud and Github Enterprise) so you should be able to get this set up. The document goes into significant detail on what triggers you can utilize as well as how to set them up.

Let me know if you run into any trouble getting configured and I'd be happy to help!

Cheers,
Daniel

Etienne Noel

This still doesn't work for next-gen projects though right?

Daniel Eads

@Etienne Noel that's correct - the status today is that advanced workflow editing (workflow triggers, for example) isn't available in next-gen projects. The current projection for this on the next-gen roadmap mentions 2020 as the "coming" estimate for the next-gen workflow editor.

Mitch Ware

@Daniel Eads We're currently using Workflow Triggers to accomplish exactly what you've explained here (via Github Enterprise) and its working very well - statuses transition as we expect them to when an associated pull request is merged. However, we're running into an issue where a developer might open two or three pull requests in small parts that merge into a feature branch, and merging those PRs cause the transition to trigger prematurely.

I'm curious if there's a way to tweak any parameters on the "pull request merged" event and filter it based on a specific branch name or regex pattern? That way, we could restrict the transition to only trigger for pull requests that target our develop branch, and ignore PR merges that occur in branches with another name/pattern.

Looking through the Workflow/Transition settings, I don't see a way to do that - is this possible?

Ivana Rodriguez

Hi all! I'm trying to accomplish something similar, but I can't seem to figure it out. Essentially, I want to transition JIRA issues into a 'QA' workflow status when changes are merged into a specific branch (ex. qa) in GitLab. Is this possible?

Olga Buslovich_h5bf56

@Daniel Eads I have the same issue as @Mitch Ware in my setup . Any suggestions , advise how to configure the trigger or automation rule that would transition the issues not for any merge but only for one that specified like DEV or QA branch.

TIA!

Olga

Olga Buslovich_h5bf56

@Etienne Noel We are experiencing the same needs. Please advise!

Thanks, Olga

Julio Kenji Bando

Hello!

I was looking for the same here then I found that it's already available in automation rules:

Jira Automation Rules

Koen_Langenhuijzen

Unfortunately this does not seem to work when using Jira Server?

Daniel Eads

Hi @Koen_Langenhuijzen - the automation rules for Server are the same, however you need to install the Automation app separately here for Jira Server and Jira Data Center (Automation is built-in in Cloud now).

@Julio Kenji Bando this is a great use of automation!

Koen_Langenhuijzen

Hi @Daniel Eads , thanks for your suggestion! However, while playing with the https://docs.automationforjira.com/rule-playground/#/ I was unable to find a trigger that is invoked when a pullrequest is merged by Bitbucket (where the branch is linked to Jira since it has been created from Jira and contains the issue key in the name).