Removing existing ticket priorities makes tickets unrenderable in queries

[jtiai]

If you remove all priorities that exist in tickets and add new ones (with different name) you can't query existing tickets anymore since many pieces of code relies on existing "priority" values in enum table.

There should be warning that operation causes bad side-effects, preferably there should be option to automatically upgrade tickets to new values.

[cboos]

Did you consider using the following TracAdmin command, instead of removing/adding?

priority change <value> <newvalue>
	-- Change a priority value

That should have taken care of the update of tickets.

Also, can you be a bit more specific about:

• which ... pieces of code relies on existing "priority" values...
• which bad side-effects

[cboos]

Plus the web admin also allows you to Modify Priority when you click on a priority value.