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? Thanks for any ideas / suggestions. Mickeyf -- 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.
