Default CC Value

[quintin@…]

In our projects we have some people that are notified of most (+-97%) of tickets/changes.

I made a patch that basically adds a "default_cc" field to the project configuration file.

This allows us to have the CC field filled in with their details, but just in case it is in the 3% of cases, we can remove it. Much more time saving than doing it the other way around.

I also attached two patches, one for the source file (tickets/api.py) and one for the config file.

[quintin@…]

Patch for ticket/api.py

[quintin@…]

Patch for trac.ini

[Johans Marvin Taboada Villca <jmt4b04d4v@…>]

Wouldn't you use smtp_always_cc and smtp_always_bcc (take a look here) instead?:

#trac.ini
[notification]
...
smtp_always_bcc = ...
...
smtp_always_cc = ...
...

It's implementation it's already done.

[quintin@…]

Yes. I did look at that.

The reason I was thinking of a default, was because in certain very rare occasions (about 3%) we don't send it to certain people. I these cases we can just remove the e-mail address.

It's just another feature that we are definitely going to use.

The idea behind this is that we have a few managers where all of us are notified of all tasks/bugs. In some rare situations when a certain manager has nothing to do with a certain component, that manager doesn't need to be on the CC list for that specific ticket. It is much easier to remove 1-3 names 3% of the time than to add 4 97% of the time.

[Emmanuel Blot]

Definitely not for 0.11.

We also need to discuss how far is going to go the notification subsystem, as there are many propositions out there, many of them being for quite specific/custom uses.
A notification API to extand the notification features through plugins would be a better option than this ever growing list of enhancements.

[sid]

I think the smtp_always_cc and smtp_always_bcc handle this in 99% of use cases. -1 for merging the special-case patch. This is one that should be in a plugin. Propose closing as a wontfix.

[osimons]

Actually, default_cc setting has been working for some time due to how ticket defaults gets populated, and it got documented as part of #7280. There should now be plenty of options to solve what you need.