Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2644

Notifications Customisable by End Users

XMLWordPrintable

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

      One thing that is currently causing us problems is the "one size fits all" Notification Scheme's that are in JIRA. Although you can define varying scheme's per project, and using watches people can decide if they want to be notified about a certain issue ... People here want to be able to do similar but at a higher level - be the execption to the scheme's rule.

      For example:

      I set groupA to be notified whenever an issue is created in projectA. This is fine, however [without admin intervention (adding them to groupA or singularly), but with "overriding approval" (eg: 'tick here to allow users to override notifications on this project')] I would like to be able to have a user decide him/herself if they get the notifications for issue creation.

      The same applies to all the various issue notification options (eg: issue closing, assigning, work logging etc).

      This idea is extensible and leads to create a scalable (overridable) notification scheme which is managed by the end users (if the option is enabled) rather than needing and administration team to get involved in notifications when they should be focused on security and auditing.

        1. screenshot.jpg
          screenshot.jpg
          46 kB

            [JRASERVER-2644] Notifications Customisable by End Users

            Christopher Juhl added a comment -

            For Jira cloud it is already possible to tweak you notifications based on: 

            1. issues, you watch
            2. issues, you are assigned to
            3. issues, where you are mentioned
            4. issues, you reported. 

            This is a highly desired feature for us, using a server version (8.3.3)!! As an admin I have complaints about the many mails from Jira on a weekly basis. 

            Christopher Juhl added a comment - For Jira cloud it is already possible to tweak you notifications based on:  issues, you watch issues, you are assigned to issues, where you are mentioned issues, you reported.  This is a highly desired feature for us, using a server version (8.3.3)!! As an admin I have complaints about the many mails from Jira on a weekly basis. 

            Jeremy Nickurak added a comment -

            Agreed. Batching of emails is not what's wanted here.

            Some users on our project want to receive emails about absolutely everything.

            Others want to only be notified when they're mentioned.

            Batching doesn't solve that. Settings that respect individual preferences is what was asked for here.

            Should this be re-opened, or should a new issue be opened with the same description?

            Jeremy Nickurak added a comment - Agreed. Batching of emails is not what's wanted here. Some users on our project want to receive emails about absolutely everything. Others want to only be notified when they're mentioned. Batching doesn't solve that. Settings that respect individual preferences is what was asked for here. Should this be re-opened, or should a new issue be opened with the same description?

            Jonas Andersson added a comment - - edited

            This is bullcrap, closing such a fundamental feature request in place of an issue that has NOTHING to do with it. If you want Jira to be less chatty, just remove the notifications. This feature specifically requested END USERS to be able to choose what notification THEY wanted.. The replacement issue does not. Can this be re-opened?

            @Dave Meyer. Any idea when "as soon as possible"  will be, or if there is a closer related ticket in place of the one you closed?

            This is a grand example of Atlassian not listining to their customers.

            Jonas Andersson added a comment - - edited This is bullcrap, closing such a fundamental feature request in place of an issue that has NOTHING to do with it. If you want Jira to be less chatty, just remove the notifications. This feature specifically requested END USERS to be able to choose what notification THEY wanted.. The replacement issue does not. Can this be re-opened? @Dave Meyer. Any idea when "as soon as possible"  will be, or if there is a closer related ticket in place of the one you closed? This is a grand example of Atlassian not listining to their customers.

            Dave Meyer added a comment -

            Hi everyone,

            I'm going to close this issue to try and consolidate discussion on the topic. Improving JIRA's email notification system is a top priority for the JIRA team. While it is not currently not in development, we do hope to work on notifications as soon as possible.

            When we address notifications, we will likely take a holistic view of the existing notification schemes/email implementation and make improvements that are described in a variety of issues on jira.atlassian.com.

            For this reason, we would like to only have to update one issue that captures all of our notifications work. Please watch JRA-1369 if you are not already.

            Thanks,
            Dave Meyer
            dmeyer@atlassian.com
            Product Manager, JIRA Platform

            Dave Meyer added a comment - Hi everyone, I'm going to close this issue to try and consolidate discussion on the topic. Improving JIRA's email notification system is a top priority for the JIRA team. While it is not currently not in development, we do hope to work on notifications as soon as possible. When we address notifications, we will likely take a holistic view of the existing notification schemes/email implementation and make improvements that are described in a variety of issues on jira.atlassian.com. For this reason, we would like to only have to update one issue that captures all of our notifications work. Please watch JRA-1369 if you are not already. Thanks, Dave Meyer dmeyer@atlassian.com Product Manager, JIRA Platform

            John Price added a comment -

            My scenario is that I have an external support vendor that creates after hours tickets via email. I don't want them to get later notifications about the tickets they create (fire and forget). Previously I was using the Jira Extended Mail Handler to set the reporter to a dummy user and white-list the sending address. However JEMH is expensive and I couldn't justify the cost.

            What I really need is to be able to say:

            "When issues are created in this project, send notifications as usual but do not send to the user afterhours@mycompany.com".

            John Price added a comment - My scenario is that I have an external support vendor that creates after hours tickets via email. I don't want them to get later notifications about the tickets they create (fire and forget). Previously I was using the Jira Extended Mail Handler to set the reporter to a dummy user and white-list the sending address. However JEMH is expensive and I couldn't justify the cost. What I really need is to be able to say: "When issues are created in this project, send notifications as usual but do not send to the user afterhours@mycompany.com".

            Linda Schmandt added a comment -

            Bugzilla has had this feature for years, and so do many other systems. It is time, Atlassian – well past time!

            Linda Schmandt added a comment - Bugzilla has had this feature for years, and so do many other systems. It is time, Atlassian – well past time!

            Daniel Varela Santoalla added a comment -

            Notification history is requested here JRA-11953, btw

            Daniel Varela Santoalla added a comment - Notification history is requested here JRA-11953 , btw

            Daniel Varela Santoalla added a comment -

            Customization may not be a problem is there was a way of knowing from the issue action who will get a notification. JRA-15380 is asking for that precisely, but it would be better if we could also check the history of notification. A tool like Footprints can do that.

            Daniel Varela Santoalla added a comment - Customization may not be a problem is there was a way of knowing from the issue action who will get a notification. JRA-15380 is asking for that precisely, but it would be better if we could also check the history of notification. A tool like Footprints can do that.

            Tibor Hegyi [META-INF] added a comment -

            Hi, Bug Watcher is our new plugin that addresses this issue. Additionally to this, it provides Project Watch, Bulk Watch and soon will implement Filter Watch features as well.

            Tibor Hegyi [META-INF] added a comment - Hi, Bug Watcher is our new plugin that addresses this issue. Additionally to this, it provides Project Watch, Bulk Watch and soon will implement Filter Watch features as well.

            John Minne added a comment -

            No kidding! It'll be 7 years in November. This shortcoming in Jira is one of the first major frustrations every new user has.

            John Minne added a comment - No kidding! It'll be 7 years in November. This shortcoming in Jira is one of the first major frustrations every new user has.

              Unassigned Unassigned
              dhardiker Dan Hardiker
              Votes:
              112 Vote for this issue
              Watchers:
              80 Start watching this issue

                Created:
                Updated:
                Resolved: