Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Tracked Elsewhere
Fix Version/s: None
Component/s: Email notifications
Labels:

Feedback Policy:

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.

Description

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

screenshot.jpg
46 kB
17/Nov/2005 1:31 PM

Issue Links

duplicates

JRASERVER-29723 Notification emails should contain more information about issues

Closed

is duplicated by

JRASERVER-15541 Personal preferences to filter notifications

Closed

JRASERVER-16866 Please add e-mail notification preferences at the individual user level

Closed

JRASERVER-18803 'Cc:' anti-pattern, please provide "No email" as a user preference

Closed

JRASERVER-20623 On attachment creation or deletion there should be a way to prevent notification emails

Closed

JRASERVER-20720 Setting Notifications at the User Level

Closed

JRASERVER-23316 Request support for per-user notification scheme

Closed

JRASERVER-26500 JIRA Spam reduction

Closed

JRASERVER-28513 Notification scheme should be customized by user not for all the project

Closed

JRASERVER-31208 user-configurable notification schemes

Closed

is related to

JRASERVER-2645 Notification Switch Off

Closed

JRASERVER-12478 Email sending improvements

Closed

relates to

JRACLOUD-2644 Notifications Customisable by End Users

Closed

JRASERVER-1369 Reduce JIRA email chatiness

Closed

JRASERVER-3791 notification scripting

Closed

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

Closed

JRASERVER-12789 Possibility choose to send email or not when notification event is triggerred

Closed

JRASERVER-14667 Add watch this issue checkbox to issue operations

Closed

JRASERVER-15840 Allow users the option to summarize their email notifications into one email.

Closed

JRASERVER-9500 Suppress notifications on issue updates

Gathering Interest

mentioned in: Page Loading...

(5 is duplicated by, 2 is related to, 8 relates to, 1 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Dan Hardiker

Votes:: 112 Vote for this issue

Watchers:: 79 Start watching this issue

Dates

Created:: 11/Nov/2003 10:33 AM

Updated:: 28/Jan/2020 7:41 PM

Resolved:: 22/Apr/2015 4:30 AM