Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Updating Workflow Status Names after multi-workflow affected change

philipf
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 26, 2023

Cloud software.

Created a new company managed prohject, and customized the unqiue workflow.

To-do = requested

In profress = partial

Done = received

--------------------------------------------

Super great, but it has no changed all other statuses with to-do, in progress, and done. 

I didn't want this. I thought my unique workflow wouldn't let this happen.

---------------

Now when I go to edit the status name, it says that this name already exists.

How can I get all of those workflows status back to their original. I can't create a new status since it will break all of the items already done in these mature boards.

-----------------

I don't have backup copies for the workflows, this new simple workflow over wrote all of the other statuses and not can't change them back.

1 answer

1 accepted

2 votes
Answer accepted
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 28, 2018

Hello,

I guess, you JQL query must be like this:

status = Resolved and status changed to Resolved before -3d

Doğucan Baskın
November 4, 2018

Hello Alexey, 

 

Thank you very much for your answer. I've tried your solution but somehow it is not working. Actually when I validate the query it finds the correct issues but somehow it doesn't change the status into "Closed".  You can see my rule below. 

Best Regards

2018-11-05 09_44_18-Automation rules - Jira.png

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 4, 2018

It will not work like this. You need to schedule this rule (use the scheduled trigger) because when your rule works the issue has been just moved to the Resolved state (it is less than 3 days)

Doğucan Baskın
November 6, 2018

Hey Alexey,

It works!! Thank you very much for your response :) 

Since you showed me using scheduler as trigger, it opened me new horizons!

Thanks again,

Have a great day.

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 6, 2018

You are welcome!

DarkSideMilk
Contributor
January 3, 2019

Can you clarify how you're using the scheduled trigger for this?

i.e. are you having this just run once a day on all matching issues that have been in the state for 3 days or is it something different?

Like Dena Campasano likes this
Doğucan Baskın
January 3, 2019

Hello,

Exactly! I am using scheduled trigger and running it every week day at 19:00 with a Cron expression: 0 0 19 ? * MON,TUE,WED,THU,FRI *

There is a statement (Only include issues that have changed since the last time this rule executed) right under the section where you write your JQL condition and we un-checked it as well. Before some of our issues were not transitioning to closed. Now everything works perfectly :)

 

Regards

Like Patrick Murphy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events