Automation: Issue hasn't been updated within the last x days - Rule

[Jeremy Powell]

TIA

Have created an automation to email assignee's when their issue in any sprint has not been updated within the last 5 days. The ruling seems to work, however, some issues updated 'yesterday' are still getting emails sent to assignees.

Using Automation I have the following:

- Scheduled 

-- Daily 9am

- Field Condition

-- Updated 

-- is Before

-- 5 days ago

- Then

-- Send email to assignee/cc:me

Is this logic right? Should Updated = is After? Is this the right field? I want to capture everything correctly and not over communicate erroneously.

[Trudy Claspill · Accepted solution]

Hello @Jeremy Powell 

Welcome to the community.

The logic is correct. The email should contain only the issues where the date/time in the Updated field is older than 9 a.m. 5 days ago.

How exactly are you determining that issues included in the email where updated "yesterday"?

[Jeremy Powell]

Thanks Trudy for the welcome and response.

How did I determine issues included were updated 'yesterday'? 

I went to the issue, and there was a comment yesterday. Am I assuming correctly that a new comment is a 'issue update' as well?

[Trudy Claspill]

Hello @Jeremy Powell 

I feel like I'm missing something in your rule. When I try to set up a Scheduled rule I have to add a JQL to select issues that will be compared against the field condition.

Do you have a JQL in this rule?

Adding a comment should update the Updated date, but you should look at the Updated date itself. That will show on the right below the Context fields.

[Jeremy Powell]

Gosh; you are correct. Apologies @Trudy Claspill 

project = "PROGRAM" and status != "Done" and sprint != "Backlog"

[Trudy Claspill]

I have not been able to recreate the problem you are experiencing.

Is it consistently getting issue updated yesterday, or is it it sporadic? Is there any commonality between the issues updated yesterday that get included and those that do not?

I suggest that you add a Log Action to your Rule to log the issue key and the value of the Updated field in your Rule audit log to see if the Rule is somehow catching the issue before the Updated field has been changed.

[Jeremy Powell]

Thanks @Trudy Claspill - I'll do that and monitor. Appreciate the assistance.