Wow, this thread got hijacked into the whole "there should be PM features in trac" debate quickly. For the record, I am against, and should be an external PM tool that connects to trac to refresh itself with ticket data....anyway
I think you want something like this: resolve = * -> inQueue (or something more descriptive, I dunno) resolve.operations = set_resolution, set_owner_to_component_owner resolve.set_resolution = fixed, duplicate, ...etc. Then probably the latter step: finalize = resolved -> closed finalize.permissions TICKET_ADMIN (or some custom permission, optionally of course) and you likely also want to add the "resolved" state(s) to your "recovery actions" reopen, unassign, etc. (i.e., reopen = inQueue, closed..... -> new) Finally, as a nice touch, you can update your roadmap states to show them differently for you or your build masters benefit in the roapmap. such as "open" ( I have a custom css group for these so they show up in a unique color, for example.) if you combine with the TypedTicketWorkflow plugin, you can even make it fancier depending on type. The ticket validation is also nice, for example to require an entry in the custom "build notes" field to move the ticket to Finalize. you also might want to add this state to any of the "ignore" fields for things like the EstimationTools plugin to consider these "closed" for the sake of calculating remaining effort, for example. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
