• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      It would be great if JIRA batched/summarized issue updates in the same way as 37Signal's Basecamp, which only sends emails on issue updates every 15 minutes. This means that once someone starts editing an issue/file/writeboard/etc, it logs all those changes for 15 minutes and then sends out the notification to everyone which shows all of the changes. Without this feature, our JIRA users at Shoes of Prey have asked to turn notifications off for Issue Updates, which is unfortunate.

            [JRASERVER-29362] summarise notification emails

            dirq added a comment -

            How is this not a feature already?

            I need a way to configure the frequency of emails that come out of jira on each ticket. When someone changes misspellings or other small things, an email is sent for EACH change. It would be great if Jira could limit and batch changes into 10 min increments and send ONE email showing the changes.

            dirq added a comment - How is this not a feature already? I need a way to configure the frequency of emails that come out of jira on each ticket. When someone changes misspellings or other small things, an email is sent for EACH change. It would be great if Jira could limit and batch changes into 10 min increments and send ONE email showing the changes.

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Stash done it with the actual release http://go.atlassian.com/stash-batch-emails
            But it seems that the jira product manager and developers ignore the need from over 500 voters... (see JRA-1369)
            Sadly, dear Jira pm and devs

            Martin, SCM Support added a comment - Stash done it with the actual release http://go.atlassian.com/stash-batch-emails But it seems that the jira product manager and developers ignore the need from over 500 voters... (see JRA-1369 ) Sadly, dear Jira pm and devs

              Unassigned Unassigned
              b5611628bc0b Todd Osborne
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: