I’ve configured an automation rule in Jira that sends an email notification to the assignee for every work item that has not been updated for more than 3 days. Since many assignees are handling a large number of open work items across multiple projects, this is generating a high volume of individual emails and flooding their inboxes.
I want to optimize this setup so that assignees receive fewer, more consolidated notifications (for example, a single summary/digest email listing all their unupdated work items instead of one email per issue). Please suggest the best way to configure Jira automation or notifications to achieve this.
Welcome to the community.
You could have the rule branch on assignee and in the branch do a lookup action. In the email action in the branch you could sent out a single email with all related issues.
So each assignee would receive a single email daily (or what your schedule is)
See this KB article as a start and example
automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next
Yes, I’ve already tried this approach, but the problem is that if an assignee has multiple pending/unupdated issues (e.g., 3 issues), they receive the same reminder email multiple times—once per issue. This creates duplicate notifications and becomes noisy instead of helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marc -Devoteam- The earlier issue has been fixed now — thank you for your support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome @Kirti Rajput
Have you tired the scheduled trigger? You can define when the emails will be sent based on the schedule that you create. If you had premium, you would include Delay action that is matching the exact use case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.