Notification Preferences

[jeff.wise@…]

My team has been using Trac for 3 months now. Overall its been a great success. However, some team members complain that they receive lots of e-mail that doesn't matter to them. This eventually leads to their ignoring Trac e-mails. An example would be when they are placed on the CC list of a ticket and later someone changes one of the ticket properties. They aren't interested in ticket property changes.

I've searched, but I haven't found a mechanism to customize the notification preferences on a per user basis. There is global configuration in TracIni, but no means for a user to indicate the kind of notifications they are interested in receiving.

I would like for a user to indicate which notifications they would like to receive:

• All (The current behaviour)
• None
• Ticket Creation
• Addition of Comments/Replies
• All Ticket properties
• Owner changes
• Milestone changes
• etc.

Please consider adding this feature to Trac. Thanks.

[sid]

Similar to, but not quite the same as #2073.

[cboos]

See also my note about user preferences settings.

Also, the level of details proposed here looks a bit to high for me, especially if in the future we have also notifications for wiki, milestone, changesets, etc.

So I'd propose a 3-levels setting, matching what we have in the timeline:

• All changes
• Only Status changes
• None

[Noah Kantrowitz (coderanger) <coderanger@…>]

If coupled with the TracObjects idea, maybe you could keep a list of (resource, field/facet) pairs to base notifications off.

[sid]

If you are cc'ed on a ticket, you will probably want to know more than just status changes. You probably want to be involved in the discussion as well, and notified of new comments. But possibly care less about ticket property changes.

[sid]

#3269 was marked as a duplicate. It contained a patch for the 0.9 branch that hardcoded cc rules to only cc on comment or description changes.

[mgood]

#4166 and #3155 have been marked as duplicates of this ticket.

[sid]

#1640 was marked as duplicate of this ticket.

[jeff.wise@…]

I'd really like to see ticket notification preferences look something like the following. Bullets are like checkboxes.

Notify me when:

• I am the ticket reporter.
• I am the ticket owner.
• I am a ticket updater.
• I am on the ticket CC list.

Notify me of:

• New comments.
• Status changes.
• Resolution changes.
• Property changes.
  • List all, including custom, properties here.

[eblot]

I think we gonna face a potential issue here: if notification content are based on user preferences, this means that we'll need to emit one email per recipient - rather than one email for all recipients, as per today.

As notification are synchronous (i.e. the web request completes when all notifications have been sent to the SMTP server), how Trac will behave with numerous recipients ?

Does this mean we need an asynchronous service to actually send the notifications? This is something that should be thought about before starting any user-based content settings.

[jeff.wise@…]

Replying to eblot:

I think we gonna face a potential issue here: if notification content are based on user preferences, this means that we'll need to emit one email per recipient - rather than one email for all recipients, as per today.

I don't understand the limitation here. Possible recipients are the reporter, owner, updater, and CC list. Use their preferences and the ticket activity to filter the list down to those who care. Then send a single e-mail to the filtered list. Unless the CC list or the set of updaters is incredibly long, it shouldn't take a significant amount of time to filter the recipient list.

[ThurnerRupert]

this feature would be also very useful for mixed user populations, like "web users" (maybe prefer notification via mail) and eclipse mylar users (get notified by mylar).

[ThurnerRupert]

maybe prevent a notification to self like addressed in #2247 is also something to consider?

[cboos]

See also #2625 (preferred format)

[Pedro Algarvio, aka, s0undt3ch <ufs@…>]

Replying to eblot:

I think we gonna face a potential issue here: if notification content are based on user preferences, this means that we'll need to emit one email per recipient - rather than one email for all recipients, as per today. As notification are synchronous (i.e. the web request completes when all notifications have been sent to the SMTP server), how Trac will behave with numerous recipients ? Does this mean we need an asynchronous service to actually send the notifications? This is something that should be thought about before starting any user-based content settings.

Something like the AnnouncerPlugin should be though of.