Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Get transition name with Automation

Hey guys, how are you doing?

Here's what I need to do: from an incident or Service Request, to be able to create a Change or a Problem.

As I have just Automation for Jira, I'm addressing it this way:

I have 2 "general" transitions (the ones that go from any status to itself) on my workflow: Create Change and Create Problem.

Then, I have an automation which creates a change, with an IF to check is the status changed from it to itself ({{changelog.status.fromString}} == {{changelog.status.toString}}), but, this is triggering both automations.

I wanted to make an if clause, to check which transition was made.

Is this possible to achieve using smart values? Or any other if condition?

1 answer

1 accepted

2 votes
Answer accepted
Andy Heinzer Atlassian Team Apr 21, 2020

Hi Vando,

I'm well, thanks for asking.  I see that you are looking to use some kind of smart value to distinguish these two different looped transitions.   I do not believe there is any such smart value that will help in regards to being able to know the name of the transition called. The available smart values in Smart values - general simply do not extend to that info.

However I think there is a way you could make this work.  I would actually look to adjust the workflow here.  In Jira Cloud you could easily change the workflow for one of these transitions so that you could add a post function of type "Update Issue custom field" to one of these transitions.  It could then change the custom field to some value that is unique to that transition.  I recommend that this post function come before the one called 'Re-index an issue..' to try to make sure we avoid any race conditions.

You could then try to check for the existence of that custom field value on the issue to see which transition executed it.  To make this work, you would need to also change the workflow of the other transition and give it a different value to set.  That way the custom field could be overwritten by each of these transitions and in turn should only trigger the automation actions of the most recent transition.

Let me know if this helps.


Hey Andy!

Took me a while to get back to this, sorry!

I just did as you said, and it worked!


Thanks so much!

Like Andy Heinzer likes this

Great Idea, Andy!

That helped me, too.


Like # people like this

That's cool, was looking for a way to make that happen too

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events