Proposal to add css classes and styles to bug titles. This would be displayed in Query output, Mass change, Dependency List, Process Bug and any other places that already have enough of the data queried and display enough of it (bug # / title). the default style should probably use color:green [or blue] for enhancements and background-color: red for (keyword: smoketest && (severity: critical || severity: blocker). netbeans.org and other collabnet sites have started using at least blue and red as colorings, and bugzilla core has added strikeout for resolved bugs. Supposing we actually went this way i wonder what fields people would want exposed. here's my suggested list: severity() keyword() votes([top5, top20, top5p, top20p, twenty, five]) priority() platform() os() target() assignee([me, watched]) reporter([me, watched]) qa([me, watched]) product() component() cc([me, watched]) below is bonus fields but would cost so much more because of a dramatic increase in queries [for open bugs relevant field=assignee, for unopen bugs relevant field=qa] these two are based on the fact that bugs can block other bugs... blocks([me, watched]) depends([me, watched]) about votes() top5 = one of the top 5 vote getting bugs in bugzilla top5p = among the top 5% of vote getting bugs in bugzilla five = has five or more votes this field would be like severity in that only one of the values would be present, it's possible that all of the values match but only the first in the list would be selected. the p values would be set based on site stats updated whenever (probably daily) and the sample space is vote getting bugs, not all bugs. (descriptive example: 10k bugzilla bugs, 200 bugs have votes, only 10 bugs could be top5p but 5 of them will be top5 instead [w/ sample space=all bugs, instead of all bugs receiving votes, all bugs would be top5p which would be useless]) about keywords. each keyword would be added separately so that css style could check for :keyword(crash):keyword(js1.5) if selectors don't work the way i want them to, replace foo(bar) w/ foo_bar if people want shorter things, something like this should work: sev key votes prio plat os goal asgn whine qa prod comp cc

->Bugzilla product...

Reassigning all of my "future" targetted bugs to indicate that I'm not presently working on them, and someone else could feel free to work on them. (sorry for the spam if you got this twice, it didn't take right the first time)

Buglists already have many classes set based on their attributes. Other pages do not need this. Having default colors based on some mysterious attributes would quickly irritate users, all having different taste and needs. WONTFIX.