Endre Bakka kirjoitti:
>> Alternately I would like to turn that feature off and only send email
>> to the person who made the edit instead of all people who edited it.
>> Is this possible and I just missed something?
> 
> No, that particular configuration is not possible AFAIK. Adding a hack  
> only requires a line or two in get_recipipents though. The notification  
> system doesn't make sense at all, and is not flexible enough.

That we all agree?

>>> Also something we've had requested - multiple owners for the same
>>> ticket (so
>>> that the ticket shows up in reports that are restricted by $USER).
>>> Abusing
>>> the cc field doesn't give us that part.
>>  From a software/IT audit perspective this troubles me. I want there
>> to be one responsible party at all times. We use special users to
>> represent departments where work has not been assigned to an
>> individual yet.
> 
> I agree - that's why I suggested an extra co-owners field instead of one  
> with multiple owners - to differentiate between people involved and the  
> one who is responsible.

Currently tickets have three participants "reporter", "owner" and cc-field.

Ticket will contain one or more participants (owner + co-owner). At 
least one (but not limited to) participant must be responsible 
participant (owner(s)). Top of that we can have listeners (cc-field).

Does "participants" differ from "listeners"? Who takes care of demotions 
and promotions to/from responsible part?

Having two "owner" and "co-owner" fields sounds more like extra 
functionality that shouldn't be really part of Trac. You can achieve 
same thing with filtering template and adding those new fields.

-- 

Jani Tiainen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to