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

Hi Atlassian,


While AUT-47  is still not yet solved, may we ask for clarification on the workaround below especially on what is meant by "Transition action" below.  I tried to look at the action "Transition Issue"  but i don't think the workaround is referring to that.  Thank you


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'.



1 answer

1 accepted

3 votes
Answer accepted

Hi @Sinio, Paul Andrew ,

In Transition issue is it possible to put smart value.

Screenshot 2021-04-12 at 15.15.43.png

Is this what you are looking for?

Regards, Marco

Thank you, @Marco Brundel!  I didn't know you can type smart values there

Like Marco Brundel likes this

This works really well as a means to support transitioning to previous status.  However, when you make the custom field, do NOT use "Number" as the type.  It will convert your status ID from 3 to 3.0, and it wont work.  Using a text field works however.

Like Marco Brundel likes this

@Marco Brundel I've tried to use it, but automation failed with:

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):

Is your string correct?

Hi @Hubert Bartkowiak 

{{issue.Previous status}}
is correct in my opinion.

I don't know why the message "Destination status could not be resolved" follows and how you can solve this.
I can see that in this and this question it is also about this message. Maybe you'll find a solution there.

Good luck and greetings, Marco

@Hubert Bartkowiak Per my reply above, while it has been some time since I had found my original fix, I believe I recall the symptom being "Destination status could not be resolved".

Can you confirm the smart value you are using is defined as text, like this:


Also, I think I recall that if you have already made the field as a Number type, you cannot change it.  You have to delete the field then re-create it.

Suggest an answer

Log in or Sign up to answer