> -----Original Message----- > From: [email protected] On Behalf Of mickeyf > Sent: 11 December 2013 15:52 > > Our legacy application used Seapine Software's Test Track. > There are plenty of things about it not to like, but it did > allow us to use a real number field for prioritizing. Thus we > could have 1.001, 1.017, 3.8923... Whatever. This meant we > could reassign and sort any number of issues to have > individual, rather than simply categorized priorities. > > Trac uses enums, and it's not practical to have more than a > handful of them since they must be individually entered. > > Is there a way to create a numeric field that could be used > with arbitrary values for prioritizing?
You can add your own fields to tickets:- http://trac.edgewall.org/wiki/TracTicketsCustomFields ...however it does not AFAIK directly support real numbers, you would probably have to use a plain text field and rewrite all of your SQL report queries appropriately (using JOINs as mentioned in the help). See #3080 for a similar issue with integer priorities:- http://trac.edgewall.org/ticket/3080 You could then remove all of the values from the built-in priority (using the admin interface) to hide that field. > Thanks for any ideas / suggestions. > > Mickeyf ~ Mark C -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
