> oh, of course you are right. if there is a wise possibility to add
> somebody else too it would be perfect. we use the owner to define
> "main responsible", and the cc to define "these people should help" -
> but this is done by a planning person.

You're right, we do need an elegant way of adding and removing others as  
well. This could be done by (ab)using the cc field. A user can change his  
own notification on a ticket through using the checkboxes, while other  
users that are notified (but not owner or reporter), is shown in the cc  
field.

I guess in your particular case, a co-owner field could be interesting  
(but maybe overkill) as well?

- Endre


> rupert.
>
> On Nov 12, 3:02 pm, Endre Bakka <[EMAIL PROTECTED]> wrote:
>> > on a ticket basis it would be overkill i guess. but set the preference
>>
>> I strongly disagree - after all, that is what the cc field is used for:
>> notification on a ticket-to-ticket basis. But instead of having to add
>> your name to a cc list, you check off a checkbox. It might be overkill  
>> for
>> owners and reporters, but hey, if the framework is already there, why  
>> not
>> give owners and reporters the chance to change notification on a
>> ticket-to-ticket basis as well.
>>
>> > at the same place where i can set the username and the email address
>> > would make a lot of sense imo. account manager plugin allows to reset
>> > the password, a nick would allow to set the user name independet from
>> > a unrememberable login-uid. is user mgt an api for writing plugins
>> > that could provide such a functionality, or i got this wrong?
>>
>> You might be right, I haven't looked closely at the code.
>>
>> - Endre
> >




--~--~---------~--~----~------------~-------~--~----~
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