Match current ticket field values in already existing entries

[jmpalacios (Juan Manuel Palacios)]

Not long ago I restructured most of the trac ticket fields to match up the most common requests from our user base (new priorities for instance, eliminating the severity field and some ticket types, new milestone and others), thus creating a sizable difference between existing tickets and new submissions. One example side effect of these changes is that the default Trac reports don't work any longer as expected to find all the requested tickets, sincethe (now) old entries are not matched by the default SQL queries (whereas new ones are).

Best solution to this problem is editing the trac db directly to update old ticket entries to match new field values, as follows:

• update ticket set type='enhancement' where type='task' or type='contribution';
• update ticket set component='deprecated' where component='uninstaller' or component='dp-cocoa';
• update ticket set priority='High' where priority='Important' or priority='Blocker';
• update ticket set priority='Normal' where priority='Expected';
• update ticket set priority='Low' where priority='Nice to have';

Another possible solution is installing the trac batchmodify plugin, found over at ​http://trac-hacks.org/wiki/BatchModifyPlugin, but I'm not sure if that has the full functionality we require (and I believe it also requires trac 0.10 at least).

-jmpp

[wsiegrist@…]

I ran the queries. The ticket.type column didnt have any needed changes btw.