[Trac] Re: WebAdmin module

[Brad Anderson]

I think that Status is a whole can of worms.  It's not isolated to 
Status.  Resolution kind of goes with it. 

Do we need protected ticket attributes?  Or at least for the Ticket 
module you happen to be working with?  If someone uses the 
PluggableModules being discussed and implements their own ticket plugin 
that does the new ticket workflow that's been discussed, they may have 
different needs to lock or protect some of the attributes.

So, which ones should we edit?  All but Status?  All but Status, Resolution?

BA

Matthew Good wrote:

>On Fri, 2005-02-04 at 00:31 +0100, Norbert Unterberg wrote:
>  
>
>>Brad Anderson schrieb:
>>
>>    
>>
>>>I've done another round of work on the Web Admin module.  It's up and 
>>>running as a test here:
>>>      
>>>
>>I guess I killed your trac server by clicking on one of the test reports 
>>that someone added there.
>>    
>>
>
>The server seems to work fine for me.
>
>  
>
>>I would not allow people to delete or add entries of the status 
>>attribute or allow to edit their value. I think the ticket states are 
>>referenced by the ticket state machine and trac may break if someone 
>>makes changes there.
>>    
>>
>
>Yes, I agree that it doesn't make sense to allow the user to edit the
>"status."  Trac is pretty dependent on the standard statuses, and
>there's no way to present any additional statuses through the interface
>either, so this currently doesn't serve any purpose and could lead to
>major breakage.
>
>  
>