Dear Trac-dev, I believe (also from the list at http://trac.edgewall.org/wiki/TracTicketsCustomFields) that most of the 'types' of custom fields are about the graphical representation of the field in the ticket page.
Is anyone aware of work to introduce some "data" types, such as integer/float/(date - but I know about http://trac-hacks.org/wiki/DateFieldPlugin). One reason we'd really like the numeric types is so that we could add some 'aggregation' options to the query pages. For example, if there was a custom field 'cost', it would be great to be able to sum() those costs on the query page to provide a total. Doing that requires to know the field is a numeric type, as well as some niceties such as validation of user input, a nicer HTML widget for the user input, and so on. The actual storage to the database backend is likely to stay as strings though, possibly... It also touches on the sorting: http://trac.edgewall.org/ticket/3080 There is also a patch that starts to go in this direction for UI validation: http://trac-hacks.org/wiki/NewCustomFieldsPatch Thanks for any pointers! Nick -- [email protected] | www.logica.com Logica UK Limited, registered in England & Wales (registered number 947968) Registered Office: 250 Brook Drive, Green Park, Reading RG2 6UA, United Kingdom -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
