I believe you can accomplish this through the workflow modifications in 0.11 (states and assignees), but I don't think you can prevent people from performing actions on it; i.e. a developer can put it to a resolved state (and you can set it so that it must enter a resolved state) and it is automatically assigned to a person, but you can't prevent the developer from going in and then setting it to a closed state.
Hopefully someone will correct me if the above is incorrect. Of course, if your developer(s) start breaking your workflow in this manner(circumventing QA by directly closing tickets) , they need to be thoroughly chewed out. Another option is for your developer to assign it to a general QA person(in whichever state), who then validates and closes the ticket. Hope that helps, James James Guyton (JGU) From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Webb Sent: Thursday, August 23, 2007 3:29 PM To: trac-users@googlegroups.com Subject: [Trac] Re: add more options to "resolve as:" in Ticket This is a question I have had. I would like to be able to move bugs to a "resolved" state by a developer and then to a "closed" state once they are verified by QA. On 8/23/07, Trac <[EMAIL PROTECTED]> wrote: Hello How I can add more options to resolve as: options in ticket? Thanks -- Jeff Webb [EMAIL PROTECTED] http://boowebb.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
