-
Suggestion
-
Resolution: Fixed
-
1,528
-
262
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
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.
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:
- Jira settings to turn off all notifications and making this link easily discoverable by adding it as a link from the email footer
- Added ability for users to configure the notifications they want to receive from Jira (issues where they are the watcher, reporter, or if you are assigned or mentioned)
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:
- Configuring Jira email notifications
- Snooze and schedule push notifications on Jira Android app
- Manage your push notifications on Jira iOS app
Best,
Irene Ongkowidjaja
Original request description
I would like to suggest the following imoprovments to the email notification:
- 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.
- 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" ).
- duplicates
-
JRACLOUD-44386 Allow Users to Opt out of Notifications in JIRA
- Closed
-
JRACLOUD-47609 Enable notification e-mails to be threaded (support in-reply-to header)
- Closed
- has a derivative of
-
JRACLOUD-59010 JIRA notification system improvement
- Closed
- is duplicated by
-
JRACLOUD-1727 Batch notifications into single e-mail
- Closed
-
JRACLOUD-3935 Daily email digest of changes
- Closed
-
JRACLOUD-7917 Roll up changes before emailing them out
- Closed
-
JRACLOUD-29362 summarise notification emails
- Closed
-
JRACLOUD-33522 Delayed sending of notifications emails
- Closed
-
JRACLOUD-34734 Send only batch notifications in planning mode
- Closed
-
JRACLOUD-42615 Group notifications made in a short period of time
- Closed
-
JRACLOUD-45414 As a user, when creating or editing issues, I want an option on whether or not to send a notification email for the action
- Closed
-
JRACLOUD-46021 Reduce number of support emails
- Closed
-
JRACLOUD-62907 Group notifications on JIRA notification's scheme
- Closed
-
JRACLOUD-70182 Only send one notification when multiple fields are edited in the New Issue View
- Closed
-
JSWCLOUD-9706 Make JIRA Software notifications less noisy
- Closed
-
JSWCLOUD-22889 Improve unread notifications to have less spam
- Closed
-
JSWCLOUD-24981 Would it be possible for you to NOT send notifications from your OWN Jira IF someone has commented ONLY "+1"
- Closed
-
JRACLOUD-69745 More control over email notifications
- Gathering Interest
- is related to
-
JRACLOUD-2644 Notifications Customisable by End Users
- Closed
-
JRACLOUD-6467 Update notification scheme to allow emails to be sent off of issue priority or add ability for notification scheme turn on/off configuration via a permission that can be granted to a project administrators
- Closed
-
JRACLOUD-7888 New user preference to turn off all email notifications - for holidays etc.
- Closed
-
JRACLOUD-22962 Reduce number of emails sent for JIRA comments
- Closed
-
JRACLOUD-62210 Please provide a way to stop receiving notification email messages for specific field changes
- Closed
-
JRASERVER-1369 Reduce JIRA email chatiness
- Closed
-
JSDCLOUD-3616 Add the ability to prevent email notification for minor comment changes
- Closed
-
JSWCLOUD-7893 Inline-Editable Fields in the Issue Detail View
- Closed
-
JRACLOUD-4304 Single email notifications for bulk edits
- Gathering Interest
-
JRACLOUD-8022 Minor change, no notifications will be sent
- Gathering Interest
-
JRACLOUD-30286 Ability to see WorkBox-like notifications in JIRA
- Gathering Interest
-
JRACLOUD-63762 Ability to unwatch a JIRA ticket from notification email
- Gathering Interest
-
JRACLOUD-77371 Don't notify sprint change on issues
- Gathering Interest
-
JRACLOUD-82675 [Tracked in Issue Links] Various notification-disabling feature requests
- Gathering Interest
-
JRASERVER-74722 Include unsubscribe link in jira.atlassian.com issue notification emails
- Gathering Interest
-
JSWCLOUD-18726 Prevent notifications with +1 comments
- Gathering Interest
- relates to
-
CONFCLOUD-14485 Digest Notifications
- Closed
-
JRACLOUD-30970 unwatch/unsubscribe/manage notifications
- Closed
-
JRACLOUD-34423 Add the ability to update issues via REST without sending notifications
- Closed
-
JRACLOUD-37777 Always use the phrase "mentioned you" in emails for comments or changes that mention me
- Closed
-
JRACLOUD-43161 self servicing notification-schemes
- Closed
-
JRACLOUD-43158 Workflow Post Function to Add or Remove Watcher
- Gathering Interest
-
JRACLOUD-78833 Option to prevent notifications when a sprint is changed.
- Gathering Interest
-
JRASERVER-69475 Jira email notification on issue description update
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...