Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-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

XMLWordPrintable

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

      Our users do not like the current notification scheme options at the project level. The 2 requests we had which we could not accommodate include:

      • Give permission to turn on/off project notification to a project level user group ( so let our project admins decide if they want to temporarily turn off email notifications for their project since they are going to reorganize issues).
      • Create a notification scheme that is triggered off of events and issue level. Meaning only send emails for issues that are at critical level or above, or only on blocker level.

      People are complaining about the frequency of emails and right now we are limited in the different email configuration options we can provide.

            [JRASERVER-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

            Otto added a comment -

            Thanks for your votes. We've reviewed the feedback and will be working on the larger theme of reducing JIRA "chattiness" (JIRA-1369).

            Thanks,
            Otto Ruettinger
            oruettinger @ atlassian dot com

            Otto added a comment - Thanks for your votes. We've reviewed the feedback and will be working on the larger theme of reducing JIRA "chattiness" (JIRA-1369). Thanks, Otto Ruettinger oruettinger @ atlassian dot com

            Ileanell Cabrera added a comment -

            Any updates on this ticket?

            Ileanell Cabrera added a comment - Any updates on this ticket?

            Amrit Nandrey added a comment -

            Is there an update on this ticket?

            Amrit Nandrey added a comment - Is there an update on this ticket?

            Amrit Nandrey added a comment -

            Matt: How did you make those changes? I want to make same change on my hosted Jira and don't see an option to do so. Can you help?

            Amrit Nandrey added a comment - Matt: How did you make those changes? I want to make same change on my hosted Jira and don't see an option to do so. Can you help?

            MattS added a comment -

            I've made changes to allow admins to select a filter when defining a notification. If the issue in an event is not part of the filter's results, then the condition fails and mail is not sent to that user or group. It's pretty smooth

            MattS added a comment - I've made changes to allow admins to select a filter when defining a notification. If the issue in an event is not part of the filter's results, then the condition fails and mail is not sent to that user or group. It's pretty smooth

            Neal Applebaum added a comment -

            This issue is, I think in part, addressed by the ability to suppress email notifications on a bulk edit. See JRA-10962.

            Neal Applebaum added a comment - This issue is, I think in part, addressed by the ability to suppress email notifications on a bulk edit. See JRA-10962 .

            Jeff Turner added a comment -

            IssueMailQueueItem could be modified to take the issue's project into account when sending the notification. I think the proper solution here is for the notification rules to be scriptable, and determined entirely by the user's business rules. That is addressed in the following issue:

            http://jira.atlassian.com/browse/JRA-3791

            Jeff Turner added a comment - IssueMailQueueItem could be modified to take the issue's project into account when sending the notification. I think the proper solution here is for the notification rules to be scriptable, and determined entirely by the user's business rules. That is addressed in the following issue: http://jira.atlassian.com/browse/JRA-3791

            Diane Griffith added a comment -

            The workaround for sending notifications for issues with certain priority, wouldn't this customization apply to all projects then? Meaning all of our projects would adhere to only sending notifications of the priority level I specified and would not allow me to customize by project? Just trying to understand the impact of the workaround you offered and if it really suits our needs. Our ideal functionality is allow some projects customize their notifications (and the events configured in it) to only notify if the issue priority is of a certain level where as other projects will want to receive notifications for all issues regardless of priority level.

            Diane Griffith added a comment - The workaround for sending notifications for issues with certain priority, wouldn't this customization apply to all projects then? Meaning all of our projects would adhere to only sending notifications of the priority level I specified and would not allow me to customize by project? Just trying to understand the impact of the workaround you offered and if it really suits our needs. Our ideal functionality is allow some projects customize their notifications (and the events configured in it) to only notify if the issue priority is of a certain level where as other projects will want to receive notifications for all issues regardless of priority level.

            AntonA added a comment -

            To stop notification from being sent one can deassociate a project from a notification scheme. At the moment the global JIRA Admin permission is required. See linked issue regarding allowing project admins to do this.

            To only send notifications for issues with certain priority one can modify com.atlassian.jira.mail.IssueMailQueueItem or the MailListener. This of course is a temporary work around. Please vote for this issue if you would like JIRA's notification schemes to be configurable based on priorioty.

            AntonA added a comment - To stop notification from being sent one can deassociate a project from a notification scheme. At the moment the global JIRA Admin permission is required. See linked issue regarding allowing project admins to do this. To only send notifications for issues with certain priority one can modify com.atlassian.jira.mail.IssueMailQueueItem or the MailListener. This of course is a temporary work around. Please vote for this issue if you would like JIRA's notification schemes to be configurable based on priorioty.

              Unassigned Unassigned
              cacfbd71a7bc Diane Griffith
              Votes:
              51 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: