NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
With a large number of projects, and lots of users, some of our project managers tend to get innuendated with e-mails. We have the project manager get notified for assigns, edits, resolved, closes, etc. Everything basically. They want to have all these notifications, because they need to know when status changes, but they don't want all of the e-mails.
What about a way to batch the changes, PRIOR to batching the sending of the e-mails. For example, say an issue is edited (component and fix for version set), then assigned to a developer with a comment, and then the developer adds another comment, all in under one minute. This would result in three e-mails, all sent out one minute from now. Why not batch the changes, and every minute poll the "notification batch", generate ONE e-mail that lists the changes made to the issue. This would significantly reduce e-mails, while still giving a project manager/lead the ability to keep up to speed on the issue. Just a thought.
JRACLOUD-1369 Reduce JIRA email chatiness
- In Progress
- is related to
JRASERVER-1727 Batch notifications into single e-mail