Mantis builds an array distinct values for each of the custom fields for the filter page. This is fine as long as the list is small. However, over time this list will get incredibly large and it is cumbersome to pick from a list at this point. Plus there may be serveral values that are the same, but possibly misspelled. We would like to have all of these results returned, not just one spelling.

A nice enhancement would be to have a config value called $g_filter_items_per_field that can be set to a default value of 25 or so that when the distinct values grows over this limit, have the filter page give the user a keyword search field instead of a drop down.