Choosing a specific transition when I have multiple going to the same status

[Steven Rhodes]

I have a workflow where I have two transitions into the Done status. One is to cancel the request and sets the resolution to cancelled (this one is available from all other statuses). The second one goes from In Progress to Done and gives you a resolution screen to set it yourself. I am trying to use automation to set the resolution for some projects using this workflow transitioning via the In Progress to Done, but when I select this in Automation for Jira, it chooses the transition that cancels the request.

How can I specify or differentiate between these two transitions? I see the transition ID of 101 for Done (and 31 for Cancel Request), but in the automation I don't know how to use the "Transition Match" feature. All the regex I have tried doesn't work.

I have tried to bypass this by using the Cancel Request transition it insists on using but I can't set the Resolution because there is only a Comment field on the transition screen (I have managed to set a generic comment though). This results in the transition to Done but means the resolution is still Cancelled.

[Michiel Schuijer · Accepted solution]

Found it, with the help of Atlassian Support:

The regex is not respected and the wrong transition is applied because of a condition:

• Only users in project role Service Desk Team can execute this transition.

The automation rule had "Actor" set to "Automation for Jira" and that is still considered an add-on and does not have the permission (project role Service Desk Team), which is why an error is produced, even if the transition does occur (with the wrong transition).

It was solved by adding an additional condition (and set it to "Any of"):

• Only users in project role atlassian-addons-project-access can execute this transition.

Now the regex is respected and it does use the correct transition.

I have asked Atlassian Support to improve & correct the error messaging so it will become clear what is really happening. In my view it should not transition at all and produce an error about missing permissions because of a set condition or something like that.

[Jeffrey Bistrong]

This worked for me, i just had to match the transition name exactly, i couldn't get it to work when the transition name had spaces in it, so replaced the space in the transition with an underscore, and now its working

[Callum Carlile _Automation Consultants_]

Hi @Steven Rhodes 

Under where you have set the Done status, there is an option to "+ add regex to distinguish between multiple transitions to the same status ".

Here, you can enter some regex based on the individual transition's name in order for the correct transition to be used.

Either this, or you can just add a post function on the specific transition to set the Resolution, meaning you don't have to 'edit' the resolution field, nor do you have to have the resolution on the transition screen (this may be the easiest solution).

Hope this helps!

[Steven Rhodes]

Thanks for your reply

I did mention that all the regex I have tried didnt work, and I can't find examples that would help me. I can see that in the example in the box it says

 .*resolv.*

And i have tried .*done.* for example

Also there are already two transitions to Done and i'd rather not add a third that sets the resolution to Done. 

[Jenny Severin]

I am having the same problem.

[Steven Rhodes]

Hi @Jenny Severin I did in the end create a new workflow as I was unable to get the automation to recognise the regex. This was a lot more work but it works now.

[Marcin Błaszczyk]

Hi Guys,

in 

.*resolv*.

 You Have to type a specific name of transition in.

@Steven Rhodes in Your issue You have to type:

.*Done*.

[Benjamin Peikes]

Why would it have to be .*Done*. and not Done ?

Wouldn't that match anything that had Done in it, or is ".*" and "*." Atlassian's regex delimiter?

[Jean-Christophe Gonzales]

same problem in march 24'

whatever the regex used I get the error : "Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)," 

[Dalhart Dobbs]

I am also having a similar issue where I have two transitions that exist between statuses dependent on post functions and validators and I want it to happen automatically if certain conditions are met. I am still getting the "Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):..." error.

[Jeffrey Bistrong]

I got this error a lot turns out the workflow conditions i put in place were blocking it. So i made a new transition just for the automation with no conditions on it except for this one and I was able to resolve my issue.

This is what my automation looks like