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.

Thank you

Sebastian

[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:

Hope this helps!

[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

[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