changes to the enum values for priorities causes issues

[mail@…]

I added my custom priorities ,and removed default priorities. Then records on TracReports are not colorized because priority-values on enum-table are not in (1-5). And the values aren't able to change.

[Matthew Good]

Well, trac-admin could provide a way to do this directly, or maybe it needs to shift the remaining enum values when an earlier one is removed. Currently you can use WebAdmin to adjust the order, or use the "priority order" command to move them up or down.

[massat]

Thanks. I have not used WebAdmin,I'll try it.

But,in my case, I couldn't adjust the order into the range from 1 to 5 with "priority order" command. Remaining priority values are 6,7,8,9,10. And I could adjust values just in range from 6 to 10. I think "priority order" command only can "replace".

regards.

[Christian Boos]

#5081 marked as duplicate.

I change this to a defect, as we don't have the ability to reuse values 1-5.

[osimons]

This has been fixed for 0.11dev in [6223] based on #2876 w/ follow-up #6490. Same issue as it happened to all the enum types. Both web and command line admin now reorders to close any gaps, always keeping an order starting with 1.

Closed as duplicate.