Multiple global transitions to same status

I want to have multiple golbal transitions to the same status, but the workflow editor won´t let me create them.

The reason is, I want to have dirrerent conditions and different post-functions. Using common transitions totally messes up the view workflow display, so I don´t want to do this.

I could export the workflow and create the global transitions in the XML - but I really don´t want to do this wink


Hope someone knows a quick fix...



2 answers

1 accepted

Hi Thomas,

I've created global transitions in this way but I've needed to make a little trick.

1.- Firts you must define the new global transition from graphical workflow interface but selecting a different status as final statusm (one status without global transition associated).

2.- Second, you must change to the text workflow interface and edit the global transition to change the destination status. In text workflow interface JIRA don't prevent you from having 2 or more global transitions with the same destination status.

3.- The workflow works ok




Hi Begoña, thanks, this works - you cannot edit the global transition in the graphical editor anymore, but that´s something I can live with. Thomas

The same information can be found here: Note: I added a status to my workflow (since all of my other statuses had global transitions). Followed the instructions and then deleted that status and it worked fine.

Hey Thomas,

I suppose you have too many status to instead create the transitions between the status and this globally-accessible status individually?

The question is, if JIRA - even if you would force it using the XML or any other way - is capable of handling multiple global transitions to the same status with different conditions and post-functions. Considering it does work though, it's also a matter of how the workflow viewer would display it and if this workflow is in any way maintainable for (other) administrators.


There are not too many statuses - the thing is there are two different global transitions to close an issue I.e. - reporters can close with resolution set to canceled - developers can close, but have to give a reason and select a resolution Conditions in validators and post-functions would also do the trick, but as they are not there this seems for me the way to go...

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,796 views 11 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot