#6128 closed enhancement (fixed)
Allow Announcer to send notifications to the user listed in a custom ticket field
| Reported by: | Kaveh | Owned by: | Robert Corsaro |
|---|---|---|---|
| Priority: | normal | Component: | AnnouncerPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.11 |
Description
This would be extremely useful in the case of having a QA contact. If AnnouncerPlugin could have something in trac.ini to specify the name of a custom field that it would point notifications to, it'd be great. I haven't yet looked into the code to see if this is easy or not, but I don't want to forget about it.
Attachments (0)
Change History (8)
comment:1 Changed 15 years ago by
| Type: | defect → enhancement |
|---|
comment:2 follow-up: 3 Changed 15 years ago by
That smtp always option would be too broad. What I mean is if you use a workflow that implements a QA owner as well as a normal owner (like bugzilla), you'd want the QA contact to be updated on that bug just like the owner. Does that help?
Basically, I want to make my own custom field in trac that I'd populate with usernames or email addresses.
comment:3 Changed 15 years ago by
| Summary: | Allow Announcer to email a custom ticket field → Allow Announcer to send notifications to the user listed in a custom ticket field |
|---|
Replying to kavehv:
That smtp always option would be too broad. What I mean is if you use a workflow that implements a QA owner as well as a normal owner (like bugzilla), you'd want the QA contact to be updated on that bug just like the owner. Does that help?
I see what you mean, and I think it would be a useful feature.
I can see other use cases for this as well. You might want the Component Owner to be notified on every ticket. Or, you might want to set a Project Manager field, so that the project lead is notified of every ticket change.
It seems like you basically want a third field, in addition to Owner and Reporter, which behaves like Owner and Reporter with respect to notifications.
There are also other requests for similar use cases in the open tickets.
comment:4 Changed 15 years ago by
| Status: | new → assigned |
|---|
Component Owner notifications are currently supported. Why not have your code add the user to the CC field? This might be useful though.
comment:5 follow-up: 6 Changed 15 years ago by
This is useful in workflows that implement a QA contact. That way someone's specified in the ticket as responsible for testing and verifying the fix that the developer was responsible for fixing. Like I said, it's similar to how bugzilla is set up. It shouldn't be hard to do, but would round out notifications in a very nice way (for those looking to use Trac in place of Bugzilla).
comment:6 Changed 15 years ago by
Replying to kavehv:
This is useful in workflows that implement a QA contact. That way someone's specified in the ticket as responsible for testing and verifying the fix that the developer was responsible for fixing. Like I said, it's similar to how bugzilla is set up. It shouldn't be hard to do, but would round out notifications in a very nice way (for those looking to use Trac in place of Bugzilla).
It might be interesting to have a workflow such that the owner is set to a QA person when the Status is changed to QA (the workflow with QA already being one of the documented Trac workflows). That would effectively result in the QA person being notified. However, if you want that QA person to be notified of all changes through the life of the ticket, this probably wouldn't work.
comment:7 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
It is not very clear what you mean. Do you just want to have all notifications sent to a specified user? If so, there is an
smtp_always_ccoption: TracIni#notification-section.