2008/7/17 Jason Winnebeck <[EMAIL PROTECTED]>: > > > From: jevans > > Any tips or gotchas for modifying a custom workflow? > > I assume adding states and actions is pretty straightforward. How > > about removing states? Would I need to migrate any tickets in the > > state to be removed one by one or is there an easier way? > > I've been wondering this myself, but it might be good to migrate tickets > anyway. There is some python code in the migrate script: > > http://trac.edgewall.org/browser/branches/0.11-stable/contrib/workflow/m > igrate_original_to_basic.py<http://trac.edgewall.org/browser/branches/0.11-stable/contrib/workflow/migrate_original_to_basic.py> > > Or, you could do it by hand. Looks like all it does is run a SQL UPDATE > on the ticket table to change status from A to B. >
Here's a couple of blog entries I put together on workflows - hope they are handy : http://nil.checksite.co.uk/archives.cfm/category/trac Regarding removing states - As Jason say, you should be able to do an SQL UPDATE across all tickets, depending on how complex the rules are for changing from one state to another. You can either write a script like the migrate_original_to_basic.py or run the query against the database using something like the firefox add-on SQLite Manager or whatever DB client you care to use. Regards Stephen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
