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

Automation for Jira: Transition to previous state



I in our workflow we have the status "Wait". When we transition to the status we set a "Wait until" date.
Once that date's been reached the automation rule executes and notifies the assignee via e-mail about the waiting period being over.

The "Wait" status can be reached from various other statuses but can always only go back to the previous one and itself.

Now we want the issue to automatically transition back to the status it came from,
(Like, if it comes from "Planning" it can only go back there.)

I already tried it with smart values from the Advanced fields documentation but that didn't work.

Specifically I tried using the value below. But it always gives me an error in the audit log that the transition needs a numerical status id.


Is there any other way to solve this?


Thanks in advance.

5 answers

2 accepted

2 votes
Answer accepted
andreas Rising Star Jul 05, 2018

Hi Sebastian,

Yes we don't really support this very well yet (see

For now the best option would be to record the previous status id in a custom field as @Christopher Jaksch mentioned.

You could use a rule like this:

  • Trigger: Field value changed with status
  • Edit issue and set the 'Previous status' field to  {{fieldChange.from}}

Then you could transition to {{issue.Previous status}} using the 'Transition action'.

We'll hopefully make this easier in future, but we've got quite a few higher priority items in our backlog currently.


@Christopher Jaksch/ @andreas

Thanks you two.

That solution worked. :)

How was this accomplished?  I'm not sure what "transition action" means. Where do I place "{{issue.Previous status}}"?

I'm using Automation Lite for JIRA.

Figured it out. Disregard.

Hi Derk 

How did you do:

 I'm not sure what "transition action" means. Where do I place "{{issue.Previous status}}"?


I can't figured it out yet :-(

Dear @Derek Mart - How can I specify {{issue.Previous status}} in the Transition Action? - All I get is copy or the statuses available but no free expression field.

Nevermind @Derek Mart - Figured it out. Thanks for your solution. 

Can anyone think of why I would get a 5-digit code for {{fieldChange.from}} for status instead of its actual two-digit code?

@Peter Reiser @Derek Mart @Jan Stähle I also see the Transaction Action but don't know where to specify {{issue.Previous status}}.  Kindly advise possibly with a screenshot.  Thanks!

Figured it out.  Never mind.  Lol.

For anyone who's losing time figuring it out, paste {{issue.Previous status}} into the dropdown field for the statuses.  It then gets recognised as a smart value.  Yes, it's not intuitive enough and took some trial and error to get it.

Like # people like this

I don't understand this.

Can u help me?

I have an issue with this approach as well, when I want to save previous status on transition, the field doesn't get updated.

Zrzut ekranu 2022-01-20 o 12.11.32.png


What should be the edit issue smart value in this case?

Ok, i found the problem.

For some reason Issue Transitioned trigger doesn't work with this - you'll have to use Field Changed for Status field - then everything works great.

I followed the steps as suggested but it doesn't seem to work for me.

My goal is, for every tickets with a status of "Cancelled", if anyone creates a comment on the ticket, the ticket will automatically reopen and transition to the previous status it was from.

Can you help me determine what I'm doing wrong?


@Boriz Agustin Can you please share your audit log for this automation?


Also please try this: Remove Edit issue fields node you have here, and create a separate automation to save the previous status into custom field. Something like this:

Zrzut ekranu 2022-01-26 o 07.45.32.png


And then just use your current automation to change and transition the issue, just without saving the previous status bit in the same automation.

Hello @Bartosz Mazurek thank you for the assist. I tried what you suggested but still it did not work.

I have created a separate rule that defines the value of Previous status through Project automation. See below:

Previous Status.JPG

And modified the original Automation:

CST Audit Log.JPG


Same issue occurs, the status still remains the same.

@Boriz Agustin It looks like the issue is that automation cannot resolve the status its supposed to transition the issue from your custom field. What did you setup your custom Previous Status field as? 

I have it set as Text Field (single line), can you check/confirm this?

@Bartosz Mazurek I have it set as Text Field (single line), I also added the Project as a context.

@Boriz Agustin Can you show how does your previous status field looks like? I mean what exactly gets written there.

@Bartosz Mazurek  I have this on:

Previous Status.JPG


Thank you in advance!

@Boriz Agustin I meant the actual data that gets stored in the field. You can for example showcase the Previous Status on issue screen, so we can see actually what gets written there for each issue.

@Bartosz Mazurek Oh OK, sorry about that. The automation seems to blank out the field. I tested this by putting an initial value to the "Previous Status" field during create.

@Boriz Agustin I think if you fix that to make sure that the field always contains correct status ID, whole thing should work correctly.

Hi @Bartosz Mazurek , yeah, that's the exact problem I'm having. I'm using "Allow all statuses to transition to this one" on the Cancelled status so setting the value on post-function is not really an option. Any ideas on what else to check on why it doesn't get populated?

@Boriz Agustin Try using the automation for saving previous status as I shared in one of previous screenshots, where it gets triggered on every transition by using When: Value changes for: Status. I think that should work correctly.

Thank you @Bartosz Mazurek , I believe that will work but the triggers available for me is limited and does not allow to target specific field change.

P.S. I was able to make this work using the {{#changelog.status}}{{from}}{{/}} and {{issue.Previous status}}

Thanks all! I was able to get this to work by using "Re-fetch issue data" between the When clause and the Transition.


2 votes
Answer accepted

Hi @spe,

as a workaround you could define a new custom field "previous status" where you enter the "string" of previous status automatically via post function.

You could use this information for your automatic rule to go back from "wait" to the previous status.

Hope that helps

Best wishes

Just jumping in on this as I have had similar issues as many on this thread!

So first off "{{fieldChange.from}}" didn't work for me. Like many others I found that "{{#changelog.status}}{{fromString}}{{/}}" was working to set the Previous Status field to what appears to be the name of the Status.

However it appears that it's setting it to a "Status - Status ID" value which when you attempt to use it in the other rule Automation doesn't like.

So I ended up using "{{#changelog.Status}}{{from}}{{/}}".

My rules that are working for peoples context:

SetPreviousStatus Rule.pngTransition to previous status rule.png

Hi all,

Can maybe someone provide a screenshot how the automation worked at your end, which trigger do you use? 

My goal similar to yours: Move an Issue from "Blocked" Status to the previous one. 

Thanks and Best,

Hey @Xheneta G_ Hyseni ,

this is what works for me:

Here I am saving the previous status to a custom field:

Zrzut ekranu 2022-05-6 o 13.01.08.png

Zrzut ekranu 2022-05-6 o 13.00.41.png


And here, in separate automation, I am changing the status to a previous one. Just the transition issue is necessary to move it, all the remaining steps are for my case when I want this to happen.

Zrzut ekranu 2022-05-6 o 13.02.02.png

Like Xheneta G_ Hyseni likes this

Hi @Bartosz Mazurek

Thanks a lot, I will give this a try.


0 votes

Hello @spe

If documentation is correct, it should work.

I would advise you to raise request to Automation support, because i didnt see many codebarrel guys on community :)

And you can try some workarounds, like create branched rule, that will checks prevous status 


and do direct transition based on status.

Hello @Mark Markov

I tried that, too. Unfortunately it doesn't work. In the audit log it always says that the issue doesn't match the compare condition...

I'll try the Automation support then.


{{issue.Previous status}} did not work for me. I'm getting an error when using the smart value as seen below. Can you please advise what I'm doing wrong?


Like Xheneta G_ Hyseni likes this

Had the same issue, it is now working after typing instead of pasting the smart variable {{issue.Previous status}} in the transition action.

works now, thanks

Suggest an answer

Log in or Sign up to answer