id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,branch,changelog,apichanges,internalchanges 919,[patch] Add a category field to the Tickets,Christian Boos,Christian Boos,"A category field can be used, well, to categorize tickets. This is a way to assign different meanings to tickets. Even today, a ticket can represent many things: * a bug * another kind of problem report * a patch * a question * a TODO * a reminder * a feature request * etc. But this is not direclty apparent. One has to go through the ticket itself to figure out, or to use tricks like the one used for this ticket (the {{{[patch]}}} prefix in the summary). Not to mention that the {{{severity}}} field is used to track the enhancements... It happens sometimes that a missing feature is of critical importance! It would be nice to have the possibility to make this categorization explicit. This would allow to search for enhancement requests or bugs, and to make that information stand out in reports too. Of course, the precise categories vary from project to project. By using {{{trac-admin}}}, one can modify the list of available categories. For instance, I use: * '''ER''' for ''Enhancement Requests'' * '''PR''' for ''Problem Reports'' * '''Task''' for something to be done * '''Event''' when something happened and I want people to know * ( ... and also '''Milestone''', because I work on the Ticket/Milestone unification, but that's a different story :) ) The proposed patch seems to work quite well, including the timeline and query module. I haven't change the default reports to include the category information yet, though. What is also missing are different icons for the different categories, which could be used in the timeline.",enhancement,closed,high,0.9,ticket system,devel,normal,fixed,ticket category,,,,,