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

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

                Created:
                Updated:
                Resolved: