On Feb 5, 3:39 am, "Cooke, Mark" <[email protected]> wrote: > > I'm very new to track and do have one small question: > > > I wonder how I could achieve following work flow: > > > currently the work flow is > > assigned -> closed > > > however I would be interested in a workflow, that allows > > > assigned -> work done -> closed (work verified) > > > if somebody fixed a defect / finished a task / or completed an > > enhancement > > I would like, that the assigned person is able to mark the ticket as > > 'I have done my work. Please verify my work and mark at as closed or > > reassign it to me' > > > If course a shortcut should always be possible. > > if an assigned ticket is closed due to 'invalid, worksforme, > > duplicate, etc.' it should of course be possble to close the ticket > > immediately. > > > Thanks a lot for any example config files / suggestions > > There is a section in the Trac wiki all about configuring your workflow, > with examples: > > http://trac.edgewall.org/wiki/TracWorkflow > > We are using this for the same reason, to add a 'testing' stage: > > http://trac.edgewall.org/wiki/TracWorkflow#Example:AddingoptionalTesting > withWorkflow > > You can also update the milestone progress indications to group tickets > differently. It's all in the wiki and easy enough to configure. In the > end we are using a modified version of one of the examples, the relevant > .ini file sections are below. > > Cheers, > > ~ Mark C > > [ticket-workflow] > ; testing.ini > ; > ; This workflow is an enhancement of the basic workflow to > ; add a "testing" stage. > ; > ; Add "table.progress td.testing { background: #bacee0 }" > ; to your roadmap.css to highlight tickets in testing on your roadmap. > ; > ; If you want "testing" tickets to count as complete in your percentage > ; calculation, uncomment the line "testing.overall_completion = true" > ; near the bottom of the file > > ; by James Smith -www.floppy.org.uk > ; Modified by Mark Cooke 1 Oct 2009 > > leave = * -> * > leave.operations = leave_status > leave.default = 4 > > reopen = testing,closed -> reopened > reopen.permissions = TICKET_CREATE > reopen.operations = del_resolution > reopen.default = 3 > > accept = new,assigned,accepted,testing,reopened -> accepted > accept.permissions = TICKET_MODIFY > accept.operations = set_owner_to_self > accept.default = 3 > > reassign = new,assigned,accepted,reopened -> assigned > reassign.permissions = TICKET_MODIFY > reassign.operations = set_owner > reassign.default = 2 > > resolve = assigned,accepted -> testing > resolve.permissions = TICKET_MODIFY > resolve.operations = set_resolution > resolve.default = 1 > > close_new = new,reopened -> closed > close_new.name = close > close_new.permissions = TICKET_ADMIN > close_new.operations = set_resolution > close_new.default = 0 > > close = testing -> closed > close.permissions = TICKET_ADMIN > close.default = 0 > > [milestone-groups] > closed = closed > closed.order = 0 > closed.query_args = group=resolution > closed.overall_completion = true > > testing = testing > testing.order = 1 > testing.css_class = new > ;testing.css_class = testing > ; Uncomment the next line if you want "testing" tickets > ; to count as complete in your percentage calculation. > ;testing.overall_completion = true > > active = * > active.order = 2 > active.css_class = open > > new = new,reopened > new.order = 3
You can also limit the "resolution" option for a ticket that goes form testing to closed, vs. the default "close" in the above example you could add > close = testing -> closed > close.permissions = TICKET_ADMIN > close.default = 0 close.operation=set_resolution close.set_resolution=verified,validated, unit_tested...etc. assuming you add these resolution states. you can then "excluded" these resolutions in the same way in the above "closed" step for all other close actions. Also, a nice feature is to use the TicketValidator plugin, and a custom field, to required the tester to enter something useful about the test(s) results, etc. but that is another layer of complexity at this stage. We use it to required a test plan number to be referenced, for example. Finally, if the 4 color options for ticket stats aren't enough (red, yellow, green, or white) you can add custom css settings for the milestone view. again, another level of complexity. it's not too hard however. just wanted you to know that option is there. -- 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.
