• 2,085
    • 79
    • Hide
      Atlassian Update – 9 January 2019

      Hi everyone,

      We're glad to announce that we’ve enabled batching of email notifications on jira.atlassian.com. This means that notifications for edits made to a single issue within the 10-minute window are now grouped together, and sent in a single email message. This feature will be shipped with Jira Server 8.0 soon. Meanwhile, you can experience it here on our public Jira instance, together with other features planned for Jira 8.0.

      What we've built

      In Jira 8.0, Jira admins will be able to reduce the number of email notifications users receive by enabling the instance-wide email batching in Jira administration. Users will be notified about all issue changes made within the 10-minute window in a single email message. The only exception is mentions. When users are mentioned in an issue, they’ll be notified immediately.

      As part of this project, you will also get a new look and feel of email notifications. For the time being, emails containing mentions use the old look and feel, but the new one will be available soon, and shipped in Jira 8.0.

      Admins will need to manually switch on batching of email notifications in Jira 8.0. In the coming releases, we will ship additional capabilities and enable batching by default.

      Please note that new notifications come with a new email subject, so if you’re using inbox filters to filter out messages, you’ll need to update them.

      What’s next

      In the coming releases, we will add support for custom fields in batched email notifications. This is important specifically for those customers who use custom fields in their customized notification email templates.

      To read about other capabilities we’ve added in Jira Software 8.0, or to download a beta version, have a look at Jira 8.0 Beta Release Notes.

      Katarzyna Derenda
      Product manager, Jira Server

       

      Show
      Atlassian Update – 9 January 2019 Hi everyone, We're glad to announce that we’ve enabled batching of email notifications on jira.atlassian.com. This means that notifications for edits made to a single issue within the 10-minute window are now grouped together, and sent in a single email message. This feature will be shipped with Jira Server 8.0 soon. Meanwhile, you can experience it here on our public Jira instance, together with other features planned for Jira 8.0. What we've built In Jira 8.0, Jira admins will be able to reduce the number of email notifications users receive by enabling the instance-wide email batching in Jira administration. Users will be notified about all issue changes made within the 10-minute window in a single email message. The only exception is mentions. When users are mentioned in an issue, they’ll be notified immediately. As part of this project, you will also get a new look and feel of email notifications. For the time being, emails containing mentions use the old look and feel, but the new one will be available soon, and shipped in Jira 8.0. Admins will need to manually switch on batching of email notifications in Jira 8.0. In the coming releases, we will ship additional capabilities and enable batching by default. Please note that new notifications come with a new email subject, so if you’re using inbox filters to filter out messages, you’ll need to update them. What’s next In the coming releases, we will add support for custom fields in batched email notifications. This is important specifically for those customers who use custom fields in their customized notification email templates. To read about other capabilities we’ve added in Jira Software 8.0, or to download a beta version, have a look at Jira 8.0 Beta Release Notes . Katarzyna Derenda Product manager, Jira Server  
    • 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.

      I would like to suggest the following imoprovments to the email notification:

      1. Have the ability to configure the notifcation period (eg. 10 minutes). Then every period the outstanding notifcations are proccessed and sent. To notifcation service should combine all updates for a single issue made by the same jira user into one email. This would reduce the volume of email notification. It is a real pain when you make 3 quick changes to a jia issue and this generates 3 emails. Thie more redundant emails jira sends the less likely people will read all of them.
      2. Jira still sends emails to me when I have made the change. Surely this should be able to turned of at least under my profile settings. (eg. "Don't notify me of change I make" ).

          Form Name

            [JRASERVER-1369] Reduce JIRA email chatiness

            akunnari added a comment -

            Could you make batch-mails for multiple issues of one preson or one organization too?

            akunnari added a comment - Could you make batch-mails for multiple issues of one preson or one organization too?

            Lucas Smithbauer added a comment - - edited

            Glad this is done... Now how about those service desk notifications and batching? Like even a minute or two delay would save me a lot of emails.

            Lucas Smithbauer added a comment - - edited Glad this is done... Now how about those service desk notifications and batching? Like even a minute or two delay would save me a lot of emails.

            Absolutely awesome!

            Hubert Seales added a comment - Absolutely awesome!

            jira guy added a comment -

            Fixed after 16 years. Someone tell Greg that this is fixed.  

             

            jira guy added a comment - Fixed after 16 years. Someone tell Greg that this is fixed.     

            Atlassian Update – 4 July 2019

            Hi and thanks for all your feedback on batched email notifications. We've improved the experience in Jira Server and Data Center 8.3 (to be released soon).

            The main changes are:

            • improving batched notifications containing mentions
            • adding instance-wide delay configuration for admins

            Email notifications for mentions are still going to be sent immediately to the mentioned user, but we've eliminated redundant information in batched emails. Until now an additional batched notification was sent to the users if they were also Assignee, Watcher or Issue Reporter, sometimes containing the same information. In the improved experience users will not receive duplicate batched notifications. The batched email will be triggered only if there was an additional issue update apart from the mention itself.

            Based on your feedback we have also added instance-wide email batching delay configuration for Jira admins. The available delay times are 2, 5, 10, 30 minutes and 1 hour. This can be configured in Jira settings in the 'Batched email notifications' section where you can also enable/disable notification email batching.

            yevgen.lasman1053119404, to answer your question, we have no plans to implement recipients limit in the Send email feature. 

            Katarzyna Derenda
            Product manager, Jira Server

            Kasia Derenda added a comment - Atlassian Update – 4 July 2019 Hi and thanks for all your feedback on batched email notifications. We've improved the experience in Jira Server and Data Center 8.3 (to be released soon). The main changes are: improving batched notifications containing mentions adding instance-wide delay configuration for admins Email notifications for mentions are still going to be sent immediately to the mentioned user, but we've eliminated redundant information in batched emails. Until now an additional batched notification was sent to the users if they were also Assignee, Watcher or Issue Reporter, sometimes containing the same information. In the improved experience users will not receive duplicate batched notifications. The batched email will be triggered only if there was an additional issue update apart from the mention itself. Based on your feedback we have also added instance-wide email batching delay configuration for Jira admins. The available delay times are 2, 5, 10, 30 minutes and 1 hour. This can be configured in Jira settings in the 'Batched email notifications' section where you can also enable/disable notification email batching. yevgen.lasman1053119404 , to answer your question, we have no plans to implement recipients limit in the Send email feature.  Katarzyna Derenda Product manager, Jira Server

            Any plans to implement batching (50 recipients limit) in Send email feature?

            Yevgen Lasman added a comment - Any plans to implement batching (50 recipients limit) in Send email feature?

            Hi @Katarzyna Derenda - That looks fine! Is there the possibility to switch this option off? So you choose if you batch them or not. And is there the possibility to change the order of the notifications in the batched mail? (one of our customer is asking about this)

            Oliver Schukay added a comment - Hi @Katarzyna Derenda - That looks fine! Is there the possibility to switch this option off? So you choose if you batch them or not. And is there the possibility to change the order of the notifications in the batched mail? (one of our customer is asking about this)

            Thank you for spotting the mistake in date daniel.schoeneck, I've corrected this in the Current Status.
            Thanks all for providing your feedback on making the delay configurable for both admins and users. We'll consider this and combine with feedback we receive after 8.0 release.

            Katarzyna Derenda
            Product manager, Jira Server

            Kasia Derenda added a comment - Thank you for spotting the mistake in date daniel.schoeneck , I've corrected this in the Current Status. Thanks all for providing your feedback on making the delay configurable for both admins and users. We'll consider this and combine with feedback we receive after 8.0 release. Katarzyna Derenda Product manager, Jira Server

            Daniel Schoeneck added a comment - - edited

            You should change the date of your announcement, it says "2018"...it is a bit confusing

             

            Daniel Schoeneck added a comment - - edited You should change the date of your announcement, it says "2018"...it is a bit confusing  

            test

            Wil Cansino added a comment - test

              tkanafa Tomasz Kanafa
              06dbb20c64ad Greg Perrott
              Votes:
              1482 Vote for this issue
              Watchers:
              644 Start watching this issue

                Created:
                Updated:
                Resolved: