Opened 11 years ago
Last modified 9 years ago
#10951 closed defect
[PATHC] Custom field order is not preserved — at Initial Version
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.11.6 |
| Severity: | normal | Keywords: | custom field order needinfo |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
It appears that _prepare_fields() in ticket/web_up.py is supposed to order the fields for the ticket property box:
- Most standard fields
- Custom fields in the order specified by the user
- Keywords
However, what I see is like:
| Reporter | Owner |
| Priority | Milestone |
| Custom 6 | Custom 7 |
| Custom 8 | Custom 9 |
| CC | Keywords |
| Custom 0 | Custom 1 |
| Custom 2 | Custom 3 |
| Custom 4 | Custom 5 |
I've displayed the names, in order, from fields in templates/ticket.html and the fields are in the wrong order as the ticket is displayed.
This may be a complex interaction of many plugins. Or one plugin's ticket handling reordering fields. (I have ~30 plugins installed.) While there may be a bug in a plugin that should not reorder fields, Trac can enforce its intended order with the attached patch.
Note:
See TracTickets
for help on using tickets.
Patch to enforce custom field order