Auto-transition an issue based on time elapsed

[BrentBot]

I am trying to create 2 automation rules in workflow in the following instances.

Automation 1

>> when the workflow for epic has been in `100% design` status for 2 business days, a comment will be placed on the epic giving warning to the user that the issue will be closed out

Automation 2

>> when the workflow for the epic has been in `100% design1 status for 3 business days a comment is made and the epic is transitioned to the closeout task from `100% design`

Not sure what happened as it was working, but maybe changed in the project require a different approach. The automations are inconsistent AND i cannot figure out a query that makes it work for applying these rules to JUST epic issue type as other workflows share some of the same status

Please see attached screenshot which shows the two automations and the error log for the 2nd automation

[Bill Sheboy · Accepted solution]

Hi @BrentBot 

I recommend adding the following to your trigger JQL as I expect you are picking up other issues and then re-test.  For a project-scope automation rule, you should not need to add the project check to the JQL.

And, I wonder if you just let JQL do the date check if that would be better, and confirm the difference using a rule condition.  Remember that the "business day" math in automation rules accounts for time zone, day of week, working day, and working hours/day...so you could be seeing some confusing behavior.

issueType = epic

Best regards,
Bill

[Matthias Gaiser _K15t_ · Accepted solution]

Hi @BrentBot,

I would check the transition part in your rule. According to the error message, the destination status can't be found.

Here are some ideas you could try:

• Have you tried deleting and recreating the transition issue action?
• Do you have special conditions/validations inside your workflow for transitioning to CLOSEOUT?

These are just some thoughts, I'd look for - maybe that already helps?

Matthias.

[BrentBot]

HI @Matthias Gaiser _K15t_ 

I do not - the only additional thing i have is a post function for setting the resolution. See attachment.

The error message shows that the rule is trying to grab another issue type it should not, but when i attempt to add the issue type of epic to the JQL in the schedule rule, it doesnt work and shows "no action performed"

for this "Have you tried deleting and recreating the transition issue action?" can you describe in further detail what you mean here?

Here is the current JQL in the schedule

status = "100% design" AND NOT status CHANGED AFTER " {{ now.minusBusinessHours(25).jqlDateTime }} "

I have tried to add project and issuetype to the expression but to no success. 

side question, should i have the checkbox `Only include issues that have changed since the last time this rule executed` selected

thank you for you help

[Matthias Gaiser _K15t_]

Hi @BrentBot,

as @Bill Sheboy suggested, the issuetype needs to be in the JQL. Since you've stated that no action was performed then. I'd suggest you test your JQL via the advanced search (go to yoursite.atlassian.net/issues).

If the JQL returns your desired result, you can try it again in the automation rule.

About your side question:

should i have the checkbox `Only include issues that have changed since the last time this rule executed` selected

I'd say I wouldn't check it now for testing, but to run it in production it's a good idea to not check the same issues again.

Were you able to resolve it? If yes, please share your solution for others to read.

[BrentBot]

i am pushing back to my sandbox and testing this tonight; though i believe i did test this before