Batched notifications in Jira Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
Due to email batching, you may notice a 3—to 10-minute wait when receiving email notifications when an event occurs in Jira.
Cause
Reduce email chatiness
To reduce the number of emails you receive, Jira Cloud will, by default, group several updates into a single email instead of sending individual emails for each update.
Critical updates (like when you’re mentioned, or an issue is assigned to you) are always sent immediately, bypassing the batching process. If you observe delays in these notifications, verify your notification settings, permissions, and email configuration to ensure accuracy. Additionally, review any overlap between Jira’s default notification behaviors and your custom automation rules to avoid unintended effects.
For the same recipient and issue, the grouping window uses an idle time and a max window time to determine when the email notification will be sent.
Unless you have selected a custom grouping window, Jira waits 3 minutes (idle time) after a change to an issue is made. If no additional changes are received, Jira sends a notification for the change. If an additional change is made before the idle time lapses, Jira resets the 3-minute idle time and listens for additional changes. The process repeats until the 3-minute idle time lapses or a maximum window time (10 minutes) is reached.
The most noticeable impact on users will be:
A short wait in receiving emails (between 3 and 10 minutes)
Lower volume of emails received, as events are grouped together (approximately 30% on average)
Note that there are some exceptions when email notifications are not batched:
Critical updates
Emails that use plain text formatting.
For more details, check out Manage your Jira personal settings.
If you experience a longer wait time when receiving email notifications (e.g., exceeding 10 minutes), start by checking your notification settings, user permissions, and suppression list to ensure everything is configured correctly. You can also verify if there’s any recent overlap between default notifications and automation rules that may cause issues. For persistent delays, gather details like the affected recipient's email and Message-ID from the delayed email and contact contact Atlassian Support for further assistance.
Was this helpful?