On Sep 15, 10:43 am, Rainer Sokoll <[EMAIL PROTECTED]> wrote: > Hi, > > I have a problem with a custom workflow that might has been covered in > the past, but I searched the archive without luck, so here we go: > I need a new status, say, "ready for QA". A developer should be able to > reassign a ticket, or to hand it over to the QA guys. > > I have this (my first attempt): > > -----8<---- > [ticket] > workflow = > ConfigurableTicketWorkflow,TicketWorkflowOpOwnerReporter,TicketWorkflowOpOwnerPrevious > > [ticket-workflow] > needinfo = new,Ready for Testing -> needinfo > needinfo.name = Need info > needinfo.operations = set_owner_to_reporter > needinfo.permissions = TICKET_ADMIN > > resolve = Ready for Testing -> assigned > resolve.name = Reassign back > resolve.operations = set_owner_to_previous > resolve.permissions = TICKET_ADMIN > > resolve_close = Ready for Testing -> closed > resolve_close.name = Close > resolve_close.operations = set_resolution > resolve_close.permissions = TICKET_ADMIN > > resolve_accepted = accepted -> Ready for Testing > resolve_accepted.name = Move to QA > resolve_accepted.operations = set_resolution > resolve_accepted.permissions = TICKET_MODIFY > -----8<---- > > My problem is (someaction).permissions. The developer who gets a ticket > assigned, must not be able to close a ticket, instead, he can either > reassign the ticket to another collegue or move it to the QA guys. These > shall be able to close a ticket, assign it back to the developer, or to > request more information from the reporter. > Right now, the developer have TICKETR_MODIFY, whilst the QA guys have > TICKET_ADMIN - but I do not want to give them TICKET_ADMIN perms :-) > Is it possible to create custom permissions like e.g. TICKET_CLOSE? > It also mybe that I cannot see the forest for the trees, so any help is > appreciated. > > Rainer
not sure exactly what you are after. but here is what I think I am hearing. you don't want to give ticket_admin to your QA guys, which I am not sure why, but ok (I mean, can't trust your QA guys?) you seem to want to require a dev to had a ticket off to QA to be verified. you want a intermediate state between "resolve" and closed, where only ticket_admin, or a QA person can actually close a ticket. making those assumptions: you probably want a workflow plugin, to prevent a developer from verifying their own ticket. (see the enterprise workflow) you probably want a custom permission, so that only "qa" folks can actually QA a ticket. workflow stuff: (btw, I searched "QA") http://groups.google.com/group/trac-users/browse_thread/thread/3c518c63ec049d65/8a827d73cd6dd790?hl=en&lnk=gst&q=QA#8a827d73cd6dd790 http://groups.google.com/group/trac-users/browse_thread/thread/ebc02f39e8cc002a/34957e2c33d50647?hl=en&lnk=gst&q=QA#34957e2c33d50647 permissions realated: (serached "permisssions") http://groups.google.com/group/trac-users/browse_thread/thread/79b11813a0cd25ab/e1710f4f7dc76cf3?hl=en&lnk=gst&q=permissions#e1710f4f7dc76cf3 http://groups.google.com/group/trac-users/browse_thread/thread/4f777072484a8f13/4d700038c029024a?hl=en&lnk=gst&q=permissions#4d700038c029024a I would recommend a special "qa" group as well to easy setting of permissions. start with the enterprise workflow, I suspect it does everything you want, probably more, which you can pair down. there is another model of interest. using master tickets, create a Master "QA" ticket type to actually QA the ticket, and a child ticket to "fix" the issue. Sometimes redundant, but then your master ticket could be a test suite, not just a single test case.... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
