Transition to the previous status of an issue using automation rules with user restiction-Jira Cloud

[Wasim Ansari]

Hi ,

I have found an article, how someone undo the current statuses but after the implemention the rule functionality as mentioned in the document is not worked. It showed an error after the rule was executed

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

SSP-63 (To Do - 10000)"

Find the doc link: https://confluence.atlassian.com/jirakb/how-to-transition-to-the-previous-status-of-an-issue-using-automation-rules-in-jira-1236599919.htm

[Wasim · Accepted solution]

Hi Folks,

I have figured it out the problem here, we have to set the owner and Actor to be same the person who will be going to execute the automation rule.

Now It is working as excepted!!

If someone has the same requirement they could use the same step to undo the transition using automation rule.

I created a custom field to store the previous status ID and put the Jira smart value  {{fieldChange.from}} to extract the status id into the old status ID.

When the condition is true it will redirecting the destination status to this status ID using these smart value {{issue.old status ID}}.

Note : create one self_loop status namely "UNDO" then perform the updated automation.

[Jehan Bhathena]

Glad to know you found the solution.

Please can you mark the Thread as accepted, so that this becomes more visible to the other community members

[Jehan Bhathena]

Hi @Wasim Ansari ,

Please can you share the workflow and which transition you're trying to perform?

The error shown is when the transition from STATUS A to STATUS B doesn't exist, in order for this to work there has to be a transition available.

[Wasim]

Thank you @Jehan Bhathena  for the quick response, the issue got resolved and I dropped the detailed answer for this!!