185041 - Would be nice if bugs blocked by other open bugs showed up as grey on bug list

Status: NEW

(Bugzilla :: Query/Bug List, enhancement)

Description

[Aubrey Alexander]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021204
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021204

An easy way to be able to see what you can work on.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Dave Miller [:justdave]]

*** Bug 185046 has been marked as a duplicate of this bug. ***

Comment 2

[Aubrey Alexander]

That way you'd know bugs you couldn't work on yet.

Additonally, it might be interesting to have bugs that block show up as purple
or another color, so you know it's important because it blocks other issues from
happening.

Comment 3

[Aubrey Alexander]

Any blocked or blocking closed bugs should not change color.

Comment 4

[Matthew Miller]

This would be great.

Alternately/additionally, is there an easy option to make blocked bugs not show
up in a given search's results at all?

Comment 5

[Scott Russell]

While colorizing entries would definitely be cute, it seems to me this would be
more useful as a filter, so I could just not see stuff I couldn't work on.

Comment 6

[Aubrey Alexander]

I actually think grey would be better, as I wouldn't want to "forget" it was
there, I just don't want my eyes to focus on things I can't do.

If I am blocking something on somebody elses list, it should appear more visible
then other entries.  This will make it more likely I'll see a bug that is
holding somebody else up.  

Very handy.

Comment 7

[Paul]

Rather than color or disappearing bugs I would rather see a new status that 
says "BLOCKED".  This way lists can be sorted and shown on the query list.  It 
could also be cool to use a different color at the same time similar to others 
like Severity=enhancment goes to italics but still shows the "enh".  Also would 
be better for sending to CSV.

Comment 8

[Aubrey Alexander]

Paul, I agree.  I just know I'd like to scan through my list and know all of the
ones I had that were, say, purple were ones I had to close because some other
bug was waiting on me.

Comment 9

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 10

[Paul]

Attachment: Patch to set the status to 'BLOCKED' when appropriate

This only changes the look of the bug list.  The true status of the bug is unchanged.

Comment 11

[Myk Melez [:myk] [@mykmelez]]

Comment on attachment 204278 [details] [diff] [review]
Patch to set the status to 'BLOCKED' when appropriate

It makes sense to identify bugs that are blocked, but I'm not sure changing their status to a status which is otherwise inaccessible from Bugzilla UI is the best approach.  Initially we should add a CSS class identifying blocked bugs and then encourage power users to style them via user stylesheets so we can gather some sense of what technique works best to identify these bugs to users.

Comment 12

[Paul]

How can the power users change it without this change?

Comment 13

[Paul]

Is this a duplicate of bug 8527?  or just really closely related?

Comment 14

[Aubrey Alexander]

>  Initially we should add a CSS class identifying blocked bugs 

This would be a perfect solution to my problem.

Comment 15

[Marc Schumann [:Wurblzap]]

See also bug 103866.