Modify ↓
Opened 19 years ago
Closed 18 years ago
#2429 closed defect (worksforme)
"trac-admin priority add foo" should honor order of execution/insersion
Reported by: | Owned by: | daniel | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | |
Severity: | normal | Keywords: | trac-admin priority |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
In my situation, I wanted more than 10 priorities (because we're all corporate and stuff here).
for i in `seq 1 15`; do trac-admin /path/to priority add P$i done
results in their order appearing as P1,P10,P2, etc.
Pleaese reference:
source:/trunk/trac/scripts/admin.py@latest#L853
to see that it uses a numerically increasing "value" field, but "value" is a text field, so if you do a
select * from enum where type='priority' order by value
it will not do as one wishes above ten items, since (lexically) 1 and 10 appear next to one another.
Attachments (0)
Note:
See TracTickets
for help on using tickets.
In 0.10, you can specify the order of appearance for priorities. This can be done using WebAdmin, or from trac-admin using: