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

Daily Mail with all Ticket with highest priority - I get more then one mail.

Sebastian Brinkmann

Hi!

I would like to get a daily mail reporting the non-closed Tickets which have status "blocker". I build a jira automation which do exactly what I want - but I can as many mails as they are tickets in the list. Actually, we have three blocker-tickets and I get three times the same mail. I don't understand, what I have to change to get only one mail per day.

Bildschirmfoto 2025-08-22 um 10.31.50.png

Thank you

Sebastian

Accepted answers

Walter Buggenhout

Hi @Sebastian Brinkmann and welcome to the Community!

If the people you need to send the email to are Jira users, it would be easier to just save your filter and create a filter subscription to send them the overview on a daily schedule. You would not even need to use automation in that case.

For such a scenario, next to the filter name click on the ... button to open this dialog and choose Add subscription:

Screenshot 2025-08-22 at 10.47.37.png

Hope this helps!

All comments

Walter Buggenhout

Hi @Sebastian Brinkmann and welcome to the Community!

For such a scenario, next to the filter name click on the ... button to open this dialog and choose Add subscription:

Screenshot 2025-08-22 at 10.47.37.png

Hope this helps!

Marc -Devoteam-

Hi @Sebastian Brinkmann

@Walter Buggenhout has a valid solution ,but if you want to do this with the automation.

Then in the email body, set it like this.

{{#lookupIssues}}
{{key}} | {{summary}}
{{/}}

Also see this KB Article as example, automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next

Duc Thang TRAN

Hello @Sebastian Brinkmann

I think your issue comes from the fact that you checked the option “Run a JQL search and execute actions for each work item in the query” on the trigger schedule.
That’s why you receive as many emails as there are tickets.

It’s strange, because in my Data Center instance I had option Process all issues produced by this trigger in bulk available in the schedule, but I don’t see it in the Cloud version.

So, either you uncheck this option and jql on the lookup issues or you follow @Walter Buggenhout suggestion to avoid consuming an extra automation.

Personally, I prefer Walter option.

Bill Sheboy

Hi @Duc Thang TRAN

You are correct: the likely cause of this symptom is the original poster included JQL in the trigger, but it should only be in the Lookup Issues / Work Items action. Removing the JQL from the trigger will solve the problem. Viewing the trigger or audit log would confirm this.

As an FYI...

The "bulk-handling" feature for the Scheduled trigger and JQL Branches is only available with Jira Server and Data Center versions, and not for Jira Cloud.

Bulk-handling was initially provided because the Lookup Issues action did not originally exist for those Jira versions. Now, the action is provided, but it has limited fields available. And so, the {{issues}} smart value for bulk-handling helps for some cases...but not for the original problem of this question.

Kind regards,
Bill

Duc Thang TRAN

Hello @Bill Sheboy

Thanks for the explanation.
I usualy managed Jira Data Center and for the last 2 years I’ve been using Jira Cloud, so I’m still learning many things.

For some needs, data center + bulk-handling might be better choice in cases where the Lookup Issues action can’t retrieve more than 100 issues.

Happy monday

Sebastian Brinkmann

Ok, good to know. Thank you!

Sebastian Brinkmann

Ok, guys, thank you! I just unchecked the option and will observe if it works as I expected.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-automation