You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is anyone aware if there is a feature or a feature request ever in the past to add buffering of e-mail sends to issue change triggers, so that they can be consolidated? We've cutover from Bugzilla to Jira and are finding the number of e-mails received from changes to xyz to be excessive. It's to the point we're now basically turning off alerting for everyone but the creator/assignee, at the request of CTO and others who have complained.
There are a few missing features that add to this problem. One is the lack of ability to add comments via the API with the "nonotify" flag like you can with some of the other API requests. This would help greatly for reducing notifications sent from automation. That, in itself is an issue as far as commenting in Jira goes, the lack of a secondary tab to put certain comments is not giving good perceptions to the end user.
But, more importantly... if I change an issue, say I cycle through the workflow of 15 steps, change the assignee, etc., it will generate 15 e-mails in the course of under 30 seconds. If the e-mail sending functionality wasn't instant and could buffer all related requests for XX seconds, it could greatly reduce the number of e-mails sent and received.