Closed Bug 329128 Opened 19 years ago Closed 10 years ago

bug number by-platform styling

Categories

(Bugzilla :: Bugzilla-General, enhancement)

Product:
Bugzilla
Component:
Bugzilla-General
Version:
2.20.1
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: eyalroz1, Unassigned)

Details

I want to be able to avoid clicking bug numbers which are specific to platforms that are uninteresting to me. If bug numbers could be styled differently when they are platform-specific, or specific to platforms which are not in a list you specify in the prefs somewhere, this would let me know I can safely ignore them. Color-coding could be nice.
Do you really want to open up this can of worms? :) Why only platforms? What about only bugs for certain products? Or only bugs whose summary matches a given regexp? etc. etc. I don't see why Platform should be treated differently than any of the other criteria for filtering bugs. Not to mention the fact that on large, public installations like b.m.o, the Hardware/OS field is often wrong, if only because it's automatically selected when the bug is filed, and then never touched again, even though the bug might be cross-platform.
I agree with Gavin.
Ok, tell you what: You let me upload a stylesheet, make all the bug number a's have class="basic-whatever-class,platform-thebugplatform,status-thebugstatus,etc" , then my own stylesheet will take care of doing whatever I want with it. How's that?
(In reply to Eyal Rozenberg from comment #3) > Ok, tell you what: You let me upload a stylesheet, make all the bug number > a's have > class="basic-whatever-class,platform-thebugplatform,status-thebugstatus,etc" > , then my own stylesheet will take care of doing whatever I want with it. > How's that? A bad idea. You would have to enumerate all possible fields because different people care about different things. This means additional SQL requests, this means conflicts when you care about several fields. And nobody else has shown any interest in this feature in the last 9.5 years.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
(sigh) Fair enough.
You need to log in before you can comment on or make changes to this bug.