Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-1369

Reduce JIRA email chatiness

XMLWordPrintable

    • 1,528
    • 262

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

       

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

       

      Atlassian Update – 26 Mar 2024

      Hi All,

      I'm delighted to announce that we have launched a Notifications settings page for Projects and Issues where you can personally manage your in-product and email notifications for Jira.

      For more details, please refer this community article.

      If you have any comments or feedback, please feel free to drop those in the above article. Thanks again for your patience and hope you find this feature helpful.

      Best regards,

      Raj

      Product Manager, Jira Software

       

       

      -- 

      19 October 2023

      Hey everyone,

      We are excited to be launching an Early Access Program (EAP) for some new changes we plan to introduce to help tackle the Jira email chattiness issue, and would like to invite all Jira Cloud admins to join our EAP. By participating, you'll have the opportunity to test out the new changes firsthand and provide us with valuable feedback to help shape the final version of this feature.

      For more details and to sign up for the EAP, please refer to our community article.

      We thank you for your continued patience and collaboration as we continue to work through this.

      I'm looking forward to your participation!

      Best regards,

      Eric
      Product Manager, Jira Software

      —

      1 June 2023

      Hi everyone,

      This is Eric again from the Jira Notifications team. Following our recent rollout of batching support for instances using a custom email domain, we’re pleased to let you know that batching support has also been added to Jira instances using a custom sender from name!

      Read all about it here: Say goodbye to inbox overload: Updates to Jira email batching

      We’re continuing to explore more ways we can reduce Jira Email Chattiness, including batching support for emails that use plain text formatting.

      Keep an eye out for more on these updates, and as always, feel free to share your thoughts and suggestions with us below.

      Thanks!

      Eric Zheng

      —

      28 April 2023

      Hi everyone,

      This is Eric from the Jira Notifications team. We're pleased to let you know that Jira instances using custom email addresses to send notifications will now have batching supported.

      This means when there are several updates for the same recipient and issue, they will be grouped into one email.

      Read more about batching

      The fix for 'custom from name' is in progress and we will provide you with an update when it is rolling out.

      Thank you for your patience.

       

      Best,

      Eric Zheng

      —

      11 August 2022

      Hi everyone,

      This is Irene from the Jira team. We are aware that this ticket hasn’t been updated for a very long time. We wanted to let you know that we’re still working on improvements to notifications, to reduce the overall noise you receive.

      I would like to start by sharing a few improvements we’ve shipped since the last update. The first is ‘batching' (email grouping). Batching of notifications means notifications from the same issue that are generated within a certain timeframe are grouped together and delivered in a single email. This reduces the number of emails you receive from a single Jira issue. Since this feature was shipped, email notifications from Jira have been reduced by 30%.

      We have read your comments and concerns; I’ll try to address them all here:

      • Batching limitation: Currently, batching isn’t available for instances where custom domains and custom ‘from email’ are used.
      • Batching timeframe: You might wait between 3-10 minutes for the issue update email to arrive, with the exception of Mentions and Issue Assigned which they will be sent immediately.

      Read more about batching and timeframe here.

      Other improvements shipped were:

      We know that, for some customer instances, this 30% reduction in email notifications and the notifications configuration still aren’t enough to reduce the noise in your inbox adequately. Particularly if you are met with the batching limitations above.

      But we want to let you know we’re working on it.

      We've kickstarted a mega project:

      • Enabling notification batching for custom domains and custom ‘from email’
      • Bringing email and push notifications together onto the same platform
      • Building greater user configuration, giving you more control over how and when you receive notifications.

      While we don’t have a specific timeline for the delivery, we will update the status here when we have additional details.

      In the meantime, here are some resources about notification configuration that Jira currently offers:

       

      Best,

      Irene Ongkowidjaja

       

      Original request description

      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" ).

        1. image-2016-08-16-10-40-40-951.png
          image-2016-08-16-10-40-40-951.png
          119 kB
        2. screenshot-1.png
          screenshot-1.png
          22 kB

          Form Name

            [JRACLOUD-1369] Reduce JIRA email chatiness

            Eric Zheng added a comment -
            Atlassian Update – 19 October 2023

            Hey everyone,

            We are excited to be launching an Early Access Program (EAP) for some new changes we plan to introduce to help tackle the Jira email chattiness issue, and would like to invite all Jira Cloud admins to join our EAP. By participating, you'll have the opportunity to test out the new changes firsthand and provide us with valuable feedback to help shape the final version of this feature.

            For more details and to sign up for the EAP, please refer to our community article.

            We thank you for your continued patience and collaboration as we continue to work through this.

            I'm looking forward to your participation!

            Best regards,

            Eric
            Product Manager, Jira Software

            Eric Zheng added a comment - Atlassian Update – 19 October 2023 Hey everyone, We are excited to be launching an Early Access Program (EAP) for some new changes we plan to introduce to help tackle the Jira email chattiness issue, and would like to invite all Jira Cloud admins to join our EAP. By participating, you'll have the opportunity to test out the new changes firsthand and provide us with valuable feedback to help shape the final version of this feature. For more details and to sign up for the EAP, please refer to our community article . We thank you for your continued patience and collaboration as we continue to work through this. I'm looking forward to your participation! Best regards, Eric Product Manager, Jira Software

            Eric Zheng added a comment -
            Status update - 1 June 2023

            Hi everyone,

            This is Eric again from the Jira Notifications team. Following our recent rollout of batching support for instances using a custom email domain, we’re pleased to let you know that batching support has also been added to Jira instances using a custom sender from name!

            Read all about it here: Say goodbye to inbox overload: Updates to Jira email batching

            We’re continuing to explore more ways we can reduce Jira Email Chattiness, including batching support for emails that use plain text formatting.

            Keep an eye out for more on these updates, and as always, feel free to share your thoughts and suggestions with us below.

            Thanks!

            Eric Zheng

            Eric Zheng added a comment - Status update - 1 June 2023 Hi everyone, This is Eric again from the Jira Notifications team. Following our recent rollout of batching support for instances using a custom email domain, we’re pleased to let you know that batching support has also been added to Jira instances using a custom sender from name! Read all about it here: Say goodbye to inbox overload: Updates to Jira email batching We’re continuing to explore more ways we can reduce Jira Email Chattiness, including batching support for emails that use plain text formatting. Keep an eye out for more on these updates, and as always, feel free to share your thoughts and suggestions with us below. Thanks! Eric Zheng

            Alexey added a comment -

            We want the ability to group/batch actions not just within one issue, but simply batch updates for all Atlasian/jira recent activity. Here is a sample: I just imported 150 issues into Jira, and asked 15 people in my team to update fields, assign them to team members etc, and my mailbox (!)exploded . 

            It would be nice to get a digest, similar to 'change/updates log on my workspace page' grouped by Ticket ID. Just add the ability in your personal profile to set the frequency of how often you get those emails 15m/60m/4h/8h. 

            For operational/fast reaction I have browser 'bell' notification and mobile APP. Let the mail be a helicopter overview of whats going on in general. 

            Alexey added a comment - We want the ability to group/batch actions not just within one issue, but simply batch updates for all Atlasian/jira recent activity. Here is a sample: I just imported 150 issues into Jira, and asked 15 people in my team to update fields, assign them to team members etc, and my mailbox (!)exploded .  It would be nice to get a digest , similar to 'change/updates log on my workspace page' grouped by Ticket ID . Just add the ability in your personal profile to set the frequency of how often you get those emails 15m/60m/4h/8h .  For operational/fast reaction I have browser 'bell' notification and mobile APP. Let the mail be a helicopter overview of whats going on in general. 

            Eric Zheng added a comment -

            Hey 668d3a7e939d, it's possible that your Jira instance may also be using another email customisation that hasn't been supported as of yet. If you'd like, feel free to send me a message at ezheng@atlassian.com and we can discuss further to find out why.

            Eric Zheng added a comment - Hey 668d3a7e939d , it's possible that your Jira instance may also be using another email customisation that hasn't been supported as of yet. If you'd like, feel free to send me a message at ezheng@atlassian.com and we can discuss further to find out why.

            Jonathan De Bondt added a comment -

            I don't know if anyone tested this but it does not seem to work for me?

             

            I still get emails on every status or comment even when they happen in the same minute?

            Jonathan De Bondt added a comment - I don't know if anyone tested this but it does not seem to work for me?   I still get emails on every status or comment even when they happen in the same minute?

            Eric Zheng added a comment -

            Hi everyone,

            This is Eric from the Jira Notifications team. We're pleased to let you know that Jira instances using custom email addresses to send notifications will now have batching supported.

            This means when there are several updates for the same recipient and issue, they will be grouped into one email.

            Read more about batching

            The fix for 'custom from name' is in progress and we will provide you with an update when it is rolling out.

            Thank you for your patience.

             

            Best,

            Eric Zheng

            Eric Zheng added a comment - Hi everyone, This is Eric from the Jira Notifications team. We're pleased to let you know that Jira instances using custom email addresses to send notifications will now have batching supported. This means when there are several updates for the same recipient and issue, they will be grouped into one email. Read more about batching The fix for 'custom from name' is in progress and we will provide you with an update when it is rolling out. Thank you for your patience.   Best, Eric Zheng

            Greg D added a comment -

            b2c7e76140ff one of the things that we do with every new Jira site that we setup, is we change the default notification scheme to only notify watchers and only notify them for Issue Assigned, Issue Resolved, Issue Commented, Issue Comment Edited, Issue Reopened, and Issue Moved. If you actually want an email, you watch an issue.

            We do not let users delete issues (so that is covered) and everything else is handled by showing in certain queues for internal assignees and reporters to streamline their workflow and reduce cognitive load (within boards and dashboards)... external emails are handled separately via JSM public comments and other automation. No need to notify of own changes and no need for the general notification overload that comes out of the box. In general, email isn't needed for regular changes and we prefer to send important things to a Slack channel or elsewhere. If everything notifies, then nothing is important.

            On top of that, we need to be able to control at-mentions (we don't want them sending emails and want to turn them off in certain projects). We also need to turn off all OpsGenie notifications (we don't even use that product and get admin emails all of the time when users are deactivated). Along those lines, we need to be able to control all admin notifications. We don't need to know when certain actions happen via email. We don't want users inviting anyone additional nor asking for apps. We have our own processes for that and want to disable those requests all together.

            Users can still choose to get notifications for things in the mobile app, but the default really should be do not email for changes. If we need to have email on, a daily digest of everything would be nice (like other users have suggested).

            Greg D added a comment - b2c7e76140ff one of the things that we do with every new Jira site that we setup, is we change the default notification scheme to only notify watchers and only notify them for Issue Assigned, Issue Resolved, Issue Commented, Issue Comment Edited, Issue Reopened, and Issue Moved . If you actually want an email, you watch an issue. We do not let users delete issues (so that is covered) and everything else is handled by showing in certain queues for internal assignees and reporters to streamline their workflow and reduce cognitive load (within boards and dashboards)... external emails are handled separately via JSM public comments and other automation. No need to notify of own changes and no need for the general notification overload that comes out of the box. In general, email isn't needed for regular changes and we prefer to send important things to a Slack channel or elsewhere. If everything notifies, then nothing is important. On top of that, we need to be able to control at-mentions (we don't want them sending emails and want to turn them off in certain projects). We also need to turn off all OpsGenie notifications (we don't even use that product and get admin emails all of the time when users are deactivated). Along those lines, we need to be able to control all admin notifications. We don't need to know when certain actions happen via email. We don't want users inviting anyone additional nor asking for apps. We have our own processes for that and want to disable those requests all together. Users can still choose to get notifications for things in the mobile app, but the default really should be do not email for changes. If we need to have email on, a daily digest of everything would be nice (like other users have suggested).

            Chris Rogers added a comment -

            Echoing Brad above, batching custom domains is the biggest complaint by far for our clients for Jira emails.

            Chris Rogers added a comment - Echoing Brad above, batching custom domains is the biggest complaint by far for our clients for Jira emails.

            Brad Hawkins added a comment -

            @Eric Zheng, batching custom domains will be a huge improvement.  Other platforms allow periodic digests (user configurable) as well, with the ability to have different rules for @mentions vs follows.  We recently moved some projects from another platform over to JIRA, and the notification spamming has been the number one complaint from our users.  

            Brad Hawkins added a comment - @Eric Zheng, batching custom domains will be a huge improvement.  Other platforms allow periodic digests (user configurable) as well, with the ability to have different rules for @mentions vs follows.  We recently moved some projects from another platform over to JIRA, and the notification spamming has been the number one complaint from our users.  

            Kristine added a comment -

            @Eric Zheng: Bulk them more instead of sending 17 mails for moving an issue through 1 workflow step. - Make it possible to change personal notification settings for more fields than available now. In my position I don't want 800 emails when I'm just reporter, but I want emails when there is a comment - or when I'm assigned to a "tester" field - or similiar.

            Kristine added a comment - @Eric Zheng: Bulk them more instead of sending 17 mails for moving an issue through 1 workflow step. - Make it possible to change personal notification settings for more fields than available now. In my position I don't want 800 emails when I'm just reporter, but I want emails when there is a comment - or when I'm assigned to a "tester" field - or similiar.

              1cfecba2ae80 Raj Kumar (Inactive)
              06dbb20c64ad Greg Perrott
              Votes:
              1574 Vote for this issue
              Watchers:
              688 Start watching this issue

                Created:
                Updated:
                Resolved: