#10326 closed enhancement (wontfix)
send ticket email notification for some users on change of certain ticket fields, only
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | notification | Version: | |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
A ticket is used for two different things here:
- topic-related discussion about certain bugs/tasks
- maintaining the project plan (working hours, estimated hours, etc.)
Some colleagues are partially interested in only 1. and always read those email notifications about new ticket comments, but don't want to always get spammed by notifications about plugin-generated ticket comments of 2., though other colleagues (like the project leader) always want to read them all.
I wish I could configure who gets which email notification, maybe having categories of comments could solve this.
Attachments (0)
Change History (8)
comment:1 by , 13 years ago
comment:3 by , 12 years ago
Milestone: | → undecided |
---|
All the tickets for {20} from last year have probably been seen multiple times by now, yet are still to be triaged…
comment:4 by , 10 years ago
Component: | general → notification |
---|---|
Milestone: | undecided → unscheduled |
comment:6 by , 8 years ago
Milestone: | unscheduled |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This can now be solved with plugin. See wiki:CookBook/Notification/Subscriptions#Unsubscribefromticketupdateswithoutcomments
comment:7 by , 8 years ago
Works well. I've had a lot of complaints from users about too many email notifications for trivial changes when running Trac in a company, and Never Notify: Only ticket props are changed would solve it.
I even have the bad effect that colleagues unsubscribed from the ticket notification because of the quite high email notification traffic due (2), although it's actually important that they keep subscribed for all activities concerning to (1).