Edgewall Software
Modify

Opened 12 years ago

Last modified 17 months ago

#6217 new enhancement

New notification/cc scheme - notification preferences per ticket

Reported by: anonymous Owned by:
Priority: high Milestone: unscheduled
Component: notification Version:
Severity: normal Keywords: notification, preferences
Cc: dbytesguard-trackhacks@… Branch:
Release Notes:
API Changes:

Description

This is an alternative/refinement of #4056.

Instead of the cc field, a logged in user will see a set of checkboxes, e.g.:

  • Notify on all changes
  • Addition of comments
  • Ticket properties
  • Owner changes
  • Status changes

By selecting one or more of these, he will receive notifications when that particular change takes place.

In his user preferences, he can set which default values should be used for when he is component owner, ticket owner, reporter or not involoved (the last can be useful if somebody wants to be notified of _all_ ticket creations for instance). But he will be able to go and change what type of notifications he want to receive on a ticket to ticket basis, also for those tickets where he is e.g. owner. This will give maximum flexibility and enable a user to fine-tune the notifications he wants to receive with a minimal effort.

For an anonymous user, todays cc field should suffice. But, if one wants to go overboard, one can create one cc field for each of the types of changes (addition of comments, owner changes etc).

Attachments (0)

Change History (10)

comment:1 by ThurnerRupert, 12 years ago

could notifications have the same posibilities than the timeline? as an rss feed is kind of a notification?

comment:2 by anonymous, 12 years ago

Keywords: notification added

With a flexible design - it should be easy to extend this to wiki pages and maybe even the repository (a hook needed?).

For wiki pages, just one checkbox to receive notification should be sufficient as you don't have the different type of changes.

For the repository, it would be nice to be able to set notification on various subfolders.

A page with a list of all notifications for the logged in user would also be convenient to make it easy to manage notifications (read: make it possible to turn off notification for multiple pages/tickets at the same time).

comment:3 by anonymous, 12 years ago

I know we have developers in my company that would prefer to only use RSS feeds for notification. Just another data point to consider.

comment:4 by anonymous, 12 years ago

For RSS feeds, it would be nice with one aggregate "Trac feed" for notifications on all tickets and wikis. With e-mail notification on a ticket-to-ticket basis, checking for changes on tickets and wikis a user has subscribed to should be fairly trivial.

comment:5 by dbytesguard-trackhacks@…, 11 years ago

Cc: dbytesguard-trackhacks@… added

Why not make RSS feeds per ticket and wiki? It should also be fairly trivial I would think.

comment:6 by Remy Blank, 11 years ago

I don't understand the previous three comments. To create an RSS feed with all ticket and wiki changes, go to the timeline, check "Ticket changes", "Ticket details" and "Wiki changes", uncheck all others, and click on "RSS feed" at the bottom of the page.

Or did you mean to create a feed with all changes to selected tickets and wiki pages?

comment:7 by Christian Boos, 9 years ago

Keywords: preferences added
Milestone: next-major-0.1Xunscheduled

comment:8 by Thijs Triemstra, 9 years ago

#9977 was a duplicate.

comment:9 by Ryan J Ollos, 5 years ago

Keywords: notification preferences → notification, preferences

comment:10 by Ryan J Ollos, 4 years ago

Owner: Emmanuel Blot removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.