how best to clean up data mining files after an updated custom workflow

[Albert Ting]

I've been trying out the new custom workflow and it works really well.  Good
timing too, since we wanted to add some new status values by the end of
June.  In particular, we want to convert the REMIND/LATER close-status
resolution values into a WAITING/PARKED open-status.

While the new flow works, I'd like to clean up the data mining files (and
perhaps the bugs_activity table) to reflect the new workflow.  It sounds
like I'll need to run a bunch of mysql commands to clean up the database and
then regenerate the data mining files.  But was wondering if there was a
better solution?

Thanks,
Albert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20070529/3f0e1964/attachment.html>