nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation for Jira: Transition to previous state

Sinio, Paul Andrew

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

Accepted answers

Marco Brundel

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

All comments

Marco Brundel

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

Sinio, Paul Andrew

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

Walker White

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.

Hubert Bartkowiak

@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?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation