ScatterToo wrote:
I'm looking for a concise flowchart of the email notification system behind Trac Tickets.In other words , who (among reporter, owner, updater, and cc: if any) gets email upon which actions (any update, any Action change, and so on). I've been deductively trying to figure this scheme out, but the lack of consistency frankly now has me baffled! In one particular project, we have automatic notification settings in the .ini turned on for reporter, owner, and updater. But I would love to see a flowchart that describes all the permutations when any one or two of these is off. In some instances, email is generated to an address when the recipient is neither the reporter, owner, or updater related to the action/ change, but may have been an owner previously. Any explanation? Is the "owner," with regard to email notification, a cumulative list? I'm getting a migraine trying to deduce this all from trial and error, so any insight would be much appreciated.
All ticket values refer to the value at the time of sending notification. This means any field changes or comments have taken effect.
The current "cc". always_notify_reporter && the current "reporter". always_notify_owner && the current "owner".always_notify_updater && each person that has ever left a comment, including the current one.
--Noah
signature.asc
Description: OpenPGP digital signature
