-
Suggestion
-
Resolution: Duplicate
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Here's an issue we're running into. People will often make a lot of sequential changes to a bug, and depending on whether or not the workflow screens directly support doing all those changes at once, subscribers to change notifications may get blasted with emails that are all related to the same bug.
Example: someone writes up a bug, goes back and edits a custom field that wasn't on the bug creation screen, attaches a screen shot, then assigns it to someone. Anyone subscribed will get four emails for one bug being created.
Suggestion: have Jira wait x minutes on the most recent change to an issue to let it "settle" before sending out a notification email, and have that email contain all the changes at once.
- duplicates
-
- Closed
-
- Closed
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
[JRASERVER-7917] Roll up changes before emailing them out
Dominic Baldin
added a comment - This is obviously popular, but no one from Atlassian has commented on this. Why was it Resolved??
Dominic Baldin
added a comment - This is obviously popular, but no one from Atlassian has commented on this. Why was it Resolved?? 
Paul Tiseo
added a comment - Barely one week into implementing JIRA at my current workplace and this has been raised by every single user multiple times.
Paul Tiseo
added a comment - Barely one week into implementing JIRA at my current workplace and this has been raised by every single user multiple times. 
Ileana Caivano
added a comment - This is critical for our implementation. We are getting bombarded with emails and it's affecting user experience. Ideally, we would love the ability to customize what type of user gets what type of change - controlling notifications at a more granular level vs. sending an email to everyone when an issue is updated for anything. Some users only want to know when it moves through the workflow vs. field edits.
Ileana Caivano
added a comment - This is critical for our implementation. We are getting bombarded with emails and it's affecting user experience. Ideally, we would love the ability to customize what type of user gets what type of change - controlling notifications at a more granular level vs. sending an email to everyone when an issue is updated for anything. Some users only want to know when it moves through the workflow vs. field edits. 
This is a great feature! In my implementation I tried to get around this by using Screens for every transition but there are always some users who edit one field at a time!
This is needed the most for inline edits. I'm fine with multiple updates if someone has gone through the quick edit screen 3 or 4 times, but if 5 values need updating and the quick edit is used for all of them in the period of 2 minutes, I don't want to be blasted 5 times in that 2 minutes when the intent was to update 5 fields.
With inline editing I'm going to use it whenever I can even if I know there are a lot of updates, because it's convenient. I think for inline edits this needs to be addressed very soon as it seems like an oversight.
Center for Teaching and Learning
added a comment - This would be a great addition - and is clearly pretty popular...
A couple ideas:
add something like the "filter subscription" options to user profile preferences for notifications digest- allowing user to choose an interval at hours, days, weeks, etc.
add an alternative option in user profile preferences to receive bulk notifications per issue at a certain interval
Center for Teaching and Learning
added a comment - This would be a great addition - and is clearly pretty popular...
A couple ideas:
add something like the "filter subscription" options to user profile preferences for notifications digest- allowing user to choose an interval at hours, days, weeks, etc.
add an alternative option in user profile preferences to receive bulk notifications per issue at a certain interval
How are the chances for this getting implemented anytime soon? The number of emails sent is quite annoying...
David Feldsine
added a comment - Not sure that digesting is what is needed here. My preference is just to mitigate the times when I multiple emails in the same minute for each different edit that happened on a single record. If a user is editing a record, and making changes, queue the change items up until the user changes focus or a timer pops and then send them all in a single email showing all the changes.
David Feldsine
added a comment - Not sure that digesting is what is needed here. My preference is just to mitigate the times when I multiple emails in the same minute for each different edit that happened on a single record. If a user is editing a record, and making changes, queue the change items up until the user changes focus or a timer pops and then send them all in a single email showing all the changes. 
Andy Brook (Javahollic Software)
added a comment - BTW, the JDigest plugin enables Jira Notification Digesting, which I think satisfies this need.
Andy Brook (Javahollic Software)
added a comment - BTW, the JDigest plugin enables Jira Notification Digesting, which I think satisfies this need. 
@Dominic - It was resolved as a duplicate. See the other linked issues.