Closed Bug 118254 Opened 23 years ago Closed 21 years ago

Disabling the severity column should not disable color coding by severity

Categories

(Bugzilla :: Query/Bug List, enhancement, P3)

2.15
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 213079

People

(Reporter: caillon, Assigned: endico)

Details

Especially after bug 36013 is fixed, it will be redundant to have the severity column enabled if you can tell what the exact severity is just by viewing the style of the bug. I tried turning that column off with the current styling, and found out they didn't work anymore! :(
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
I think a quick fix to this would be this patch: Change line 1280 in buglist.cgi -my @selectcolumns = ("id", "groupset"); +my @selectcolumns = ("id", "groupset", "severity", "priority"); This forces those columns to be in the resulting data set. I tested it by taking out the severity and priority columns and my bug was still hilighted correctly. If this is it, I will gladly supply the patch...
Depends on: 130276
bug 213079 has a patch and is approved for checkin. *** This bug has been marked as a duplicate of 213079 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
No longer depends on: 130276
clearing milestone on wontfix/duplicate/worksforme/invalid
Target Milestone: Bugzilla 2.18 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.