On Sep 4, 2009, at 7:34 PM, RJOllos wrote:
> > On Sep 4, 1:01 am, Roger Oberholtzer <[email protected]> > wrote: >> So this means that everyone who adds a ticket needs to add >> @some_group >> to the CC field of each ticket? I guess I could change the defaults >> for >> new tickets to have the default group we want. But this will only >> apply >> to new tickets - unless I edit all existing tickets and add it. >> Right? > > Yes, I think so. > > The `default_cc` parameter I suggested would automatically add the > group to the CC field. The limitation would be the same group would > be added to the CC field every time. I have set this up. I now need to add this to all existing tickets. Time to hone up my sql skills. > > You might be able to use one of the plug-ins to set a different group > to the CC field depending on the ticket type or another parameter. We > should look on trac-hacks and see if there is anything that would > accomplish this. What is the rule you want for assigning a group to > the CC field? Is it dependent on the ticket type, component, > username, ....? I am ok with just one default when a ticket is added. After that, users are on their own. The basic functionality is going to be pretty much what I felt was missing: users can elect to be notified of all ticket additions. So I will simply have one joinable group that is there by default. > > You could probably do a database insert to take care of existing > tickets. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
