Automation

gemma.whitfield April 8, 2024

Hi,

I'm trying to use the 'Task is due in X days - send email reminder' automation template so that we can get email reminders when a ticket is due in 3/5/7 days.

However, we are not getting any reminders, even though tickets are due. 
I have looked in the audit logs and it says the rule had a successful run. I can't seem to find where I'm going wrong here and why we are not receiving the emails?

Any help would be much appreicated.

Thanks

2 answers

0 votes
gemma.whitfield April 22, 2024

Hi both,

I am using Jira's pre-built template, I did not build this rule from scratch.

This is the JQL statement for the first LookUp issues action:

duedate <= endOfDay({{numberOfDaysBeforeDueInclusion}}) AND statusCategory != done AND assignee != empty

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 8, 2024

Hi Gemma - Welcome to the Atlassian Community!

Can you share an image of your rule here? 

gemma.whitfield April 9, 2024

Hi John,

Thanks!

Here is my rule:

 

Screenshot 2024-04-09 at 10.38.34.pngScreenshot 2024-04-09 at 10.38.39.png

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

Thanks for that. Can you share the details of the Audit log when it runs?

And the email @live.com doesn't arrive either? 

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 10, 2024

Also, you probably want to log out the values returned from the lookupIssues to be sure there is indeed values there. 

gemma.whitfield April 11, 2024

Thanks John, here is the latest audit log, it does indeed seem to be related to the lookupIssues as you suggested:

 

Screenshot 2024-04-11 at 15.03.52.png

Bill Sheboy
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 Leaders.
April 11, 2024

Hi @gemma.whitfield 

Adding to John's suggestions...

Would you please show the action where you create the variable?

Would you please copy the JQL statement you are using for the first Lookup Issues action, and write that to the audit log?  That will help confirm what JQL is being used when the rule runs.

And...why use a variable when the value could be used directly in the JQL for the lookup issues action?

Kind regards,
Bill

Like John Funk likes this
gemma.whitfield April 22, 2024

Hi both,

I am using Jira's pre-built template, I did not build this rule from scratch.

This is the JQL statement for the first LookUp issues action:

duedate <= endOfDay({{numberOfDaysBeforeDueInclusion}}) AND statusCategory != done AND assignee != empty

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2024

We need the details of the Variable - not the JQL statement. 

gemma.whitfield April 22, 2024

Variable name: numberOfDaysBeforeDueInclusion

Value: 3

 

 

Screenshot 2024-04-22 at 15.37.07.png

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 23, 2024

Why don't you just use 3 as the value instead of creating a variable and assigning the value of 3 to the variable? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events