[#JRA-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

JIRA

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

Created: 21/Apr/05 01:44 PM Updated: 26/May/08 05:59 AM

Component/s:

Permissions Security

Affects Version/s:

3.1.1

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Weblogic 8.1 SP3

Issue Links:

Duplicate

This issue duplicates:

JRA-3791 notification scripting

This issue is duplicated by:

~~JRA-13589~~ Suggested feature - Apply notification schemes by issue priority.

~~JRA-7033~~ Add ability to filter notification based on issue type and priority.

Part

This issue is incorporated by:

JRA-3156 Required: Project Group Administrator

Reference

This issue relates to:

JRA-2115 Ability to create Notification Scheme based on issue priority

This issue is related to:

JRA-10962 No Email For Bulk Change Permission

JRA-2644 Notifications Customisable by End Users

Participants:	Anton Mazkovoi [Atlassian], Diane Griffith, Jeff Turner [Atlassian] and Neal Applebaum
Since last comment:	98 weeks, 5 days ago
Support reference count:	6
Labels:

Description

« Hide

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.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 01/May/05 07:10 PM

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.

[ Permlink | « Hide ]

Diane Griffith - 02/May/05 07:09 AM

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.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 04/May/05 10:16 PM

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

[ Permlink | « Hide ]

Neal Applebaum - 29/Aug/06 10:01 AM

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