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

spe

Hello

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.

{{#changelog.status}}{{from}}{{/}}

Is there any other way to solve this?

Thanks in advance.

Accepted answers

Christopher Jaksch

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
Chris
STAGIL

andreas_qezsu8

Hi Sebastian,

Yes we don't really support this very well yet (see https://codebarrel.atlassian.net/browse/AUT-47).

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.

Cheers,
Andreas

All comments

Mark Markov

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

{{#changelog.status}}{{fromString}}{{/}}

and do direct transition based on status.

spe

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.

Thanks.

Christopher Jaksch

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
Chris
STAGIL

andreas_qezsu8

Hi Sebastian,

Yes we don't really support this very well yet (see https://codebarrel.atlassian.net/browse/AUT-47).

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.

Cheers,
Andreas

spe

@Christopher Jaksch/ @andreas

Thanks you two.

That solution worked.

Derek Mart

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

Derek Mart

I'm using Automation Lite for JIRA.

unknown

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,
Xheneta

Bartosz Mazurek_g611dp

Hey @[deleted],

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

unknown

Hi @Bartosz Mazurek

Thanks a lot, I will give this a try.

Best,
Xhen

sergio.peschiera

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

Tristan_xkqixz

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

Lewis Cook_vntdgk

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.png Transition to previous status rule.png

Steven Camilleri_bavoui

image (1).png

Hi, I hope this helps someone! I saw a lot of people doing multiple rules. I have managed to do it in a single rule! It works as expected.

Kevin Dickson_o2tc47

Hi Community,

Just been reading through this chain of threads, and wondering how this is possible when the initial poster said: "..The "Wait" status can be reached from various other statuses but can always only go back to the previous one and itself..."

Unless there is a transition back to the previous state in the workflow, how is this possible?

Lewis Cook_vntdgk

They never shared a workflow so I guess we can assume one of the following:

It's a very messy workflow with transitions enabled to all other applicable statuses from the "Wait" status presumably with some validation that would limit your target options back to "Wait" or the previous status
They've used a lot of "All" transitions on their statuses and put in conditions to limit the target options based on previous status
It's not a technically enforced process just an agreement of how to handle it (seems least likely).

From working on other similar automation rules it will error if it's unable to find/resolve the target destination status. Either because there isn't a transition or the "previous status" field has become stale/outdated.

Where I've implemented similar there a few sections of the workflow where I didn't technically want it to transition to the previous status, so I put in workflow post functions (or automation rules) to set the previous status field to the desired Status ID I would want it returned to.

Kevin Dickson_o2tc47

Post functions sounds like a great idea, I'll look into that.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-cloud

addon-com.codebarrel.addons.automation