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: Transition Issues to Archive after Done for 3 Days

Donna Benton

I cannot understand why these simple rules are not working for the automation I'm trying to accomplish. I merely want to transition issues to Archive after they have been transitioned to Done for 3 days. This should be so easy and I know I'm going to kick myself after one of you tell me what is missing here... Ideas?

Accepted answers

Bill Sheboy

Hi @Donna Benton

You are trying to do something 3 days after the transition to done, but your trigger is on the transition to done now. That happens at that moment in time.

To do what you ask, you could change to use a scheduled trigger (e.g., running once per day), and use JQL to identify any Done issues to move to Archived on that day.

trigger: scheduled daily, with JQL to find the issues
action: transition to Archived

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Donna Benton

You are trying to do something 3 days after the transition to done, but your trigger is on the transition to done now. That happens at that moment in time.

To do what you ask, you could change to use a scheduled trigger (e.g., running once per day), and use JQL to identify any Done issues to move to Archived on that day.

trigger: scheduled daily, with JQL to find the issues
action: transition to Archived

Kind regards,
Bill

Donna Benton

Thanks, Bill. That makes sense. I'll give it shot!

Donna

Donna Benton

Well, I am still not finding success. Here is what I've got.

Bill Sheboy

Are you using Jira Cloud, Server, or Data Center version?

Would you please post an image of the audit log details, showing what happened when the rule executed? That may indicate what is happening.

And...some tips:

For a rule like yours, the separate branch is not needed. Instead you may put that JQL in the scheduled trigger directly. The advantage of that approach is the rule will not run unless there are issues to process.
One great thing about scheduled triggers is we can test them immediately, without waiting until the schedule happens (i.e., 5pm in your rule). You can select the button Run Rule to immediately try them, speeding up the development and testing cycle.