[PATCH] Custom field order is not preserved

[Chris.Nelson@…]

It appears that _prepare_fields() in ticket/web_ui.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.

[Chris.Nelson@…]

Patch to enforce custom field order

[Chris.Nelson@…]

By the way, the change I made to display field order in the ticket template is:

trac/ticket/templates/ticket.html

@@ -159 +159 @@
               <td headers="h_owner">${ticket.owner and authorinfo(ticket.owner)
               </td>
             </tr>
+         <span py:with="fieldorder=[f['name'] for f in fields]">
+             ${pprint('fieldorder:%s' % fieldorder)}
+          </span>
             <tr py:for="row in group(fields, 2, lambda f: f.type != 'textarea')
               py:with="fullrow = len(row) == 1">
               <py:for each="idx, field in enumerate(row)">

I wish I could figure out how to write to trac.log from a template but this is the best I could do.