-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yes, that might work. But if not asking for re-ordering standard fields,
I'm still fond of the capabilities of DynamicFieldsPlugin. It could
certainly do anything Keban is asking for.
Keban, you see, there is no standard approach for this. Various
developers found different solutions, that might work for you. Not
altering the template would be better for you, and I suggest it to you
because I know about the hassle of updating templates after upgrading
Trac. This is especially nasty, if you don't have documented your
modifications _exactly_, so you'll probably end-up re-inventing it over
and over again.
Trac plugins do this template mods at run-time that might work
flawlessly even across Trac upgrades, or you'll just need to update your
plugin. I use this approach for rather heavily customized ticket views
with success on some of my own Trac applications.
Make your own (Trac plugin) choice, please, and ask for a configuration
recipe afterwards, if you feel that you need it.
Steffen Hoffmann
[1]
http://trac-hacks.org/wiki/DynamicFieldsPlugin
iEYEARECAAYFAlC9JGMACgkQ31DJeiZFuHeUmQCg1Vi4alaNtLb1RAL7ucExXXBC
1sMAnArvOZTR9q4kIKUKGRmUnmlnvbIz
=rhGH
-----END PGP SIGNATURE-----