204864 - Display flags (requests) in long_list ("long format" of bug list)

Status: RESOLVED FIXED

(Bugzilla :: Query/Bug List, enhancement)

Description

[Matt Phillips]

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.1; X11; en_US, en_GB, en)
Build Identifier: Bugzilla Version 2.17.4 

There's no way to display flags in either query format...  In the normal format flags can't be 
added to the column list, and in the long format flags don't appear.  It'd be useful to have bug 
flag statuses showing at least on the log format. 

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Julian Gorfajn]

Actually, I would love to have the flags in the short format. We are using flags
to track updates on multiple versions of the product and it would be nice to see
that in the table. It wouldn't be any wider than if someone puts their keywords
in that table (which is already possible).

Comment 2

[Frédéric Buclin]

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

Comment 3

[Frédéric Buclin]

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

Comment 4

[Frédéric Buclin]

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

Comment 5

[Bernd Kuemmerlen]

Bug 265354 comment 1 has a nice patch (attachment 162778 [details] [diff] [review]) which adds Flag[+|-|?]
columns to the normal buglist.

This patch works nicely for me in Bugzilla 2.18

BTW, is there a point in resolving a lot of bugs as duplicate of a bug without
Assignee? Seems to me that nobody will ever look at this bug here (target
Milestone is "Future", no Assignee)

Comment 6

[Frédéric Buclin]

(In reply to comment #5)
> This patch works nicely for me in Bugzilla 2.18

As I said in the other bug, this patch sugggests to add 3 columns to the bug
list, one per flag status '+', '-' and '?'. IMO, we should have one column which
contains *all* flags about the bug itself (bug flags) and a second column which
contains *all* flags about *non* obsolete patches only (attachment flags).


> BTW, is there a point in resolving a lot of bugs as duplicate of a bug without
> Assignee?

Yes, for two reasons. First, newer bugs are *usally* (that means if there is no
good reason to do otherwise) marked as dupes of the oldest one in respect to the
reporter who first found a bug or suggested a new feature. Second, the assignees
in the other bugs are the default assignees (myk and justdave) which most of the
time do not spend a minute to think about these bugs. In other words, they were
not working on them.


I may take this bug myself as soon as my "to do" list decreases a bit. But it
won't be before 2.20. So if someone else wants to take it, please do! :)

Comment 7

[Christian :Biesinger (don't email me, ping me on IRC)]

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

Comment 8

[Frédéric Buclin]

Fixed by blocker.