I am aware of the sage admonishment to avoid creating too many custom fields. I am also aware that one mark of success for software is that it is used to solve problems largely unanticipated during its inception. Issue tracking tools outside of software development SUCK (a severe understatement). There are some environments (e.g., savvy law firms) that would benefit from additional configurability in work flow and data capture. Please consider adding the ability to create and manipulate custom fields for: 1) Users (specific case captured by #372417) 2) Products 3) Components 4) Comments Ideally, custom fields associated with entities other than bugs (issues) would benefit from any implemented (e.g., #287326, #291433) or planned (e.g., #396974, #398557) enhancements. I am not familiar enough with the architecture to propose an approach. If I have time, I will delve, but it is unlikely.

Oops...the following bugs should have been referenced more carefully in the previous comment (for auto-linking): Bug 372417 Bug 287326 Bug 291433 Bug 396974 Bug 398557

You know you can also write your own extensions for specific use cases? I could see how this could be useful for users, products or components (though not really how such custom fields would be used or displayed outside edit*.cgi), but I don't see how this could be useful for comments.