Condition on automations using transition name

[Martin Vali]

Hi

I want o have 2 types of transitions (Deep RCA needed; Quick RCA needed) from same status "Extinguished" to another status "In RCA"

Jira does not understand the condition

[Gor Greyan · Accepted solution]

Hi @Martin Vali

Thanks for the question.

Unfortunately, this isn't possible in Jira Cloud Automation.

The Work item transitioned trigger only exposes the From and To statuses. Although there are two different workflow transitions leading from Extinguished to In RCA, the transition name itself isn't available as a smart value that can be used in conditions. That's why {{transition. name}} doesn't return the expected value.

You can find this suggestion, vote, and watch it.
https://jira.atlassian.com/browse/JIRAAUTOSERVER-39

If you need to distinguish between these two paths, one common approach is to update a custom field during the transition to indicate which path was taken. Your automation can then evaluate that field instead of the transition name.

[John Funk · Accepted solution]

Hi Martin,

Supposedly that should work. Try adding the Condition as a separate component instead of being bundled with the Trigger. And don't use the " quote marks in your value in the Condition. 

Now, having said that I think I just realized you are tying to tell which transition was just executed? If that's the case, the rule will not look at that, but what is available from the current status. If you are really wanting to check which transition just happened, then there should something different about them that could be used in the condition. 

[Mikael Sandberg · Accepted solution]

{{transition}} is not a smart value that automations recognize, but there are a couple of options to know which transition was used. You could set a custom field with the name, you could create a custom event and then use {{eventType}}, or you could use a property via the API that you can access via {{issue.{property}}}. Another option is to set a label that is then removed once the automation triggers.