New notification/cc scheme - notification preferences per ticket

[anonymous]

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

[ThurnerRupert]

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

[anonymous]

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

[anonymous]

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

[anonymous]

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.

[dbytesguard-trackhacks@…]

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

[rblank]

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?