JIRA Workflow Triggers and Bitbucket Commits/Pull-Requests Edited

I"m setting up a simple WF in JIRA:

NEW <-> IN PROGRESS <-> IN REVIEW <-> TBV -> CLOSED

There is also a loopback from TBV to IN PROGRESS.

I've set up the right WF triggers so the Bitbucket (BB) commits and PR's transition the JIRA issues, but I've having one problem.  My transition to IN PROGRESS is "common" (all states that transition to IN PROGRESS use the same transition).  That transition has triggers enabled so that it transitions for BB branch-create and commits (either one).  The idea is from NEW to IN PROGRESS, it's usually a branch create that should transition.  But, from IN REVIEW or TBV, another commit resets the issue back to IN PROGRESS.

Another trigger for a PR Merge will transition from IN REVIEW to TBV.

The problem is that in BB, the PR Merge generates another commit, so JIRA sees 2 triggers, and follows both transitions:

  • a PR Merge to transition to TBV
  • a commit to transition (back) to IN PROGRESS

Is there anyway to control this without setting up separate transitions to IN PROGRESS with different triggers?  I really like reusing transitions in a WF as much as possible.

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,681 views 18 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you