I would like to control the ABSOLUTE order of the custom and out of
the box fields. I know in ini file, I can specify the ORDER using
".order" under the [ticket_custom] section. I searched through google,
but could not find anything....help! I want to do something like this:
any idea?? In the ticket properties, I want the fields to show up with
the following order
Priority Keywords
Severity Assign to
Component --empty--
Custom field 1 Custom field 2
Custom field 3 Custom field 4
Custom field 5 --empty--
Custom field 6 --empty--
Custom field 7 --empty--
Thanks in advance!
Hope this helps,
Geoff
<?cs if: field.label == 'O/S' ?><?cs set:fullrow = 1 ?>
<?cs /if ?>
'O/S' is the name of my custom field and the next field now got pushed
right below it!
Hi, I'm also looking for a way to define a custom order for non-custom ticket fields and custom ticket fields.
As for the custom there is this possibility:
project = select
project.order = 5
But there is no way to define that for internal fields such as type and priority. It would be nice to set the internals in [ticket-custom] as well by defining the order only.
There was already a request like this before:
https://trac-hacks.org/ticket/2642#comment:11
Is redefining the CS template the only way? Which template define the ticket fields?
br, Mo
Hi, thank you for your fast solution.
How can I install a single .py as Plugin?
Trying to understand how to configure it, would this be a correct configuration by listing all fields in the desired order?
[ticket]
field_order = type, priority, milestone, component, version, keywords, cc
I don't even know the internal names of the builtin fields.
BR,
Mo
field_order = type, customer, project, version, component, owner, priority, platform, parents, keywords, development, developer, review, reviewer, test, tester, documentation, author, service, serviceer, integration, integrator, propagation, customer, cc
Hi,
Jun Omae, I appreciate that TracTicketFieldsLayoutPlugin as it is quite useful for our case, it would be moreover useful to have a custom column count instead of the fixed 2 column layout currently. However there is a big blocker about this plugin as it says it will not be ported to any Trac 1.4+. We are currently on 1.0.9 but I would avoid in any case to have more dependencies that could break future updates. I currently have many addons I need to keep up to date. So having in mind that this plugin will be obsolete soon I would not like getting used to it...
@RjOllos : I found some major issue with the field_order variable of your plugin. The ticket mask is implicitly different when creating a new ticket or modifying an old one, as the old one has missing the owner field.
Having this order:I completely depend on the field order for having test and tester side by side in the 2-column layout. Any idea? I could move the owner right to the end of the list, but then I would need an empty dummy, like a keyword 'null' or something.
field_order = type, customer, project, version, component, owner, priority, platform, parents, keywords, development, developer, review, reviewer, test, tester, documentation, author, service, serviceer, integration, integrator, propagation, customer, cc
Best regards.
Mo