Reducing Email Noise from Sprint Automation
Overview
When Sprint Automation moves or updates many issues at sprint boundaries, Jira can send a large number of notification emails.
This article explains:
Where those emails come from,
What you can change in Jira,
How users can filter them out in email clients.
1. Where the emails come from
Sprint Automation does not send email directly.
When the app:
Updates the Sprint field,
Closes or starts a sprint,
Moves issues to another sprint or backlog,
Jira treats these actions as normal issue updates.
Jira then:
Fires notification events (e.g. Issue updated, Issue moved),
Checks the project’s notification scheme,
Sends emails to users configured as recipients for those events.
The sender or actor often appears as Sprint automation (Jira) or similar, but the emails are still standard Jira notifications.
2. How to reduce notification volume
There’s no Sprint Automation toggle for “no emails”, but you have three practical levers:
Project notification schemes,
Users’ personal Jira email preferences,
Email client rules.
Option A: Adjust the project’s notification scheme (admin)
As a Jira admin, identify the impacted projects.
In each project (company-managed), find and open the notification scheme.
Look for events that trigger on automation updates, especially:
Issue updated
Issue moved
Any custom workflow events triggered by sprint close/start
For those events:
Remove overly broad recipients (e.g. “All Watchers”, “Current Assignee”),
Replace them with more targeted groups or roles, if appropriate.
Important:
This affects all actions that fire those events – not just Sprint Automation updates.
If you need different behavior for one project, consider:
Cloning the current notification scheme,
Tweaking the clone,
Assigning it only to projects that use Sprint Automation.
Option B: Users adjust their Jira personal email settings
For individual heavy users:
Go to Jira profile → Personal settings / Email notifications.
Reduce or turn off some categories of notifications (depending on your plan).
Confirm which projects and events are most important; leave those enabled.
This reduces noise only for that user and doesn’t change what others see.
Option C: Filter emails in your mail client
This is often the lowest-risk approach when you don’t want to change Jira settings.
Examples:
In Gmail or Outlook, create a rule that:
Matches the sender (e.g., your Jira notification email address or “Sprint automation (Jira)” in the display name).
Optionally matches part of the subject or body.
Automatically:
Moves emails to a separate folder/label,
Marks them as read,
Or archives them.
Because DiViM’s app doesn’t send separate email, filtering on Jira’s notification sender+pattern is usually safe.
3. Troubleshooting: which event is sending this email?
If you’re not sure which event is causing an unwanted notification:
Open the email.
Click through to the issue in Jira.
Open the History tab on the issue.
Find the change that occurred at the same timestamp as the email:
Sprint field changed,
Status changed,
Assignee changed, etc.
In the project’s notification scheme, locate the event that corresponds to that cause (commonly Issue updated).
Review which roles/groups are configured as recipients for that event.
Then decide whether to:
Adjust the scheme (admin),
Ask users to adjust their personal settings,
Or rely on email filters.
4. Limitations
Currently, you cannot:
Turn off only “Sprint Automation emails” while leaving all other Issue updated emails,
Configure custom email content or recipients directly from within the Sprint Automation UI.
All mail behavior is controlled by Jira’s standard notification system and users’ email clients.