• 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.

      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.

            [JRASERVER-1727] Batch notifications into single e-mail

            Hi Team,

            Thank You for having this facility of batch e-mailing in Jira now. It is of great use.

            The issue which I have faced is I set the batch e-mail notification setting to 1 hr, but when I restarted the Application server, it was again changed back to 10 minutes. Can you tell me how to make this setting permanent as it is not changed everytime server is rebooted?

            Thank You!!

            swati gupta added a comment - Hi Team, Thank You for having this facility of batch e-mailing in Jira now. It is of great use. The issue which I have faced is I set the batch e-mail notification setting to 1 hr, but when I restarted the Application server, it was again changed back to 10 minutes. Can you tell me how to make this setting permanent as it is not changed everytime server is rebooted? Thank You!!

            I support this request. Gathering of mails for 5 minutes and send it in one would lead to a higher acceptance of Jira mails.

            Werhahn Baratella added a comment - I support this request. Gathering of mails for 5 minutes and send it in one would lead to a higher acceptance of Jira mails.

            Please add the ability to batch emails for changes made within a short timespan, i.e. a minute. For example, when I change the workflow status of a ticket, re-assign it, and then add a comment, it should result in one digest email instead of three individual ones.

            Daniel Gasienica added a comment - Please add the ability to batch emails for changes made within a short timespan, i.e. a minute. For example, when I change the workflow status of a ticket, re-assign it, and then add a comment, it should result in one digest email instead of three individual ones.

            Igor Masen added a comment -

            Our users welcomed the batched notifications in Confluence, why Atlasssian does not bring this for JIRA? Todays JIRA notifications create a lot of waste and spendings on it.

            Igor Masen added a comment - Our users welcomed the batched notifications in Confluence, why Atlasssian does not bring this for JIRA? Todays JIRA notifications create a lot of waste and spendings on it.

            As a product owner I had to make an email filter to delete all Jira emails. So now I need to check all updated issues once every week and it makes me wonder, how is that different from using Google Docs or just a notebook? Please do this feature, or I will switch to other solution just because I cannot take it anymore.

            Saulius Pacekajus added a comment - As a product owner I had to make an email filter to delete all Jira emails. So now I need to check all updated issues once every week and it makes me wonder, how is that different from using Google Docs or just a notebook? Please do this feature, or I will switch to other solution just because I cannot take it anymore.

            MM (PREM) added a comment - - edited

            please ignore that, I took the wrong ticket...

            MM (PREM) added a comment - - edited please ignore that, I took the wrong ticket...

            shaymandel added a comment -

            The cost of the EMQ plugin is outrageous for our team (we have a 500 users license). This should definitely be considered a part of the core functionality and not a plugin that adds additional cost. Seems like Jira is a not top of mind for Atlassian any more. Frustrating.

            shaymandel added a comment - The cost of the EMQ plugin is outrageous for our team (we have a 500 users license). This should definitely be considered a part of the core functionality and not a plugin that adds additional cost. Seems like Jira is a not top of mind for Atlassian any more. Frustrating.

            This is particularly bad when a user makes a series of changes to the same issue. This is a side effect of your design choice to commit all changes immediately, which is nice functionality in the UI, but when for many updates to an issue I get three emails within 5 seconds of each other overall that's a horrible user experience. I'd rather have to explicitly save an issues after every set of changes and not get multiple emails.

            cori schlegel added a comment - This is particularly bad when a user makes a series of changes to the same issue. This is a side effect of your design choice to commit all changes immediately, which is nice functionality in the UI, but when for many updates to an issue I get three emails within 5 seconds of each other overall that's a horrible user experience. I'd rather have to explicitly save an issues after every set of changes and not get multiple emails.

            This has gotten to be a bigger and bigger issue, and is now intolerable. Everyone (including me, the admin!) just ignores/trashes any email from JIRA without reading it. I cannot see how this serves any purpose or makes your product better. It only provides a negative user experience, especially for new users.

            Jeremy Marquis added a comment - This has gotten to be a bigger and bigger issue, and is now intolerable. Everyone (including me, the admin!) just ignores/trashes any email from JIRA without reading it. I cannot see how this serves any purpose or makes your product better. It only provides a negative user experience, especially for new users.

            Yes, please add this functionality to JIRA. While notification e-mails can be very useful, the noise level undermines their usefulness.

            As it is now, I'm notified every time a user touches the record. If a user creates a story, edits the description, and then adds a screenshot for each record, I'm getting three notifications when one would do. For a developer who's working on multiple projects, this can make the inbox a downright depressing place.

            Allowing us to configure JIRA to collect notifications and send every x minutes would be extremely helpful.

            Kevin Canney added a comment - Yes, please add this functionality to JIRA. While notification e-mails can be very useful, the noise level undermines their usefulness. As it is now, I'm notified every time a user touches the record. If a user creates a story, edits the description, and then adds a screenshot for each record, I'm getting three notifications when one would do. For a developer who's working on multiple projects, this can make the inbox a downright depressing place. Allowing us to configure JIRA to collect notifications and send every x minutes would be extremely helpful.

              Unassigned Unassigned
              cdd2f78debc9 Adam Harvey
              Votes:
              54 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: