I have an automation that I want to look up issues where the due date is within the next 60 days. * Scheduled to run at 1:00 am * Lookup "Renewal Date[Date]" <= 60d - when validate returns 2 issues * I want to e-mail the results to a group of specific users. Nothing gets sent. The audit logs state No Actions Performed.

Sometimes rules can get "glitched" due to many edit / publish cycles, breaking something behind the scenes in the JSON. Often the ways to check that align with what you tried: * Disable the rule, wait 5 minutes, reenable it, and test. When that does not help... * Disable the rule, recreate it from scratch, and test

@Brian Taylor if it helps to you can you hit accept answers so that others can reach

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; } } }

Jira Auotmation Does Not send an e-mail

Brian Taylor_5wqrpi

I have an automation that I want to look up issues where the due date is within the next 60 days.

Scheduled to run at 1:00 am
Lookup "Renewal Date[Date]" <= 60d - when validate returns 2 issues
I want to e-mail the results to a group of specific users.

Nothing gets sent. The audit logs state No Actions Performed.

Screenshot 2025-03-04 at 4.33.16 PM.png

Accepted answers

All comments

Bill Sheboy

Hi @Brian Taylor

If you try the JQL in the Lookup Issues standalone to test it with View All Issues, does it return any issues?

If so, in which project(s) are the issues? If the issues are in multiple projects and the rule is a single-project scope rule it cannot "see" the issues. The rule scope will need to be changed, and your Jira Site Admin will need to change the rule scope.

Kind regards,
Bill

Pasam Venkateshwarrao

Hi @Brian Taylor

In the Automation rule you have used Wrong JQL,The correct JQL is

Screenshot 2025-03-05 at 12.52.22 PM.png

Pasam Venkateshwarrao

@Brian Taylor is helped to solve your query still you are looking another solution

Brian Taylor_5wqrpi

Pasam - The change in the query did not change the outcome. When I validate the query, I still get two issues with your query as I did with mine.

Pasam Venkateshwarrao

@Brian Taylor can you try with this Automation rule

Screenshot 2025-03-05 at 6.22.42 PM.png

Brian Taylor_5wqrpi

Bill,

Thanks for the feedback. It is for a single project. I rewrote the automation this morning from scratch, and now it appears to be working.

Thanks for the help.

Screenshot 2025-03-05 at 9.27.40 AM.png

Bill Sheboy

Sometimes rules can get "glitched" due to many edit / publish cycles, breaking something behind the scenes in the JSON. Often the ways to check that align with what you tried:

Disable the rule, wait 5 minutes, reenable it, and test. When that does not help...
Disable the rule, recreate it from scratch, and test

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud

jira-automation