Matthew Tuck [:CodeMachine] Reporter
	Description • 24 years ago

It seems people are still using [bug flags] on description or whiteboard fields,
_even where_ there are keywords present for the same thing.  The only purpose I
see this serving is so they can see the result on their bug list.

Hopefully I don't have to articulate why this is a suboptimal situation.  It
pains me greatly to see that keywords have failed to replace tracking bugs and
description/whiteboard flags when they just need a little TLC to do so.

In this case, I think there are two problems.  One is the difficulty of
bookmarking a specific set of columns in Bugzilla, which is already filed as bug
#12284.  The description field is pretty much guaranteed to be present.

The other is that keyword fields can be really big and contain lots of keywords
that are irrelevant to the query at hand.  In a very real sense each keyword
field is an unrelated separate boolean field, and we should be able to treat
them the same as we treat any other separate fields.

This means in "Change Columns" we should be able to specify which keywords we're
interested in, ie:

(a) all
(b) none
(c) only X, Y, ...
(d) all except X, Y ..

These could either appear as they do now as one field, or as separate fields
with ticks or crosses (or some appropriate alternative).  However the latter
might take up too much space, especially if your bug list headers aren't
scattered.

	Andreas Franke (gone)
	Comment 1 • 23 years ago

-> Bugzilla product, Bug List component, reassigning.

	Andreas Franke (gone)
	Comment 2 • 23 years ago

See also bug 69253 "E-mail notification prefs on individual keywords."

	Andreas Franke (gone)
	Comment 3 • 23 years ago

See also bug 61447: Column width control in bug lists. That bug has a patch.
Marking dependency for now (just for tracking).

	Dave Miller [:justdave]
	Comment 4 • 21 years ago

Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)

	Dave Miller [:justdave]
	Comment 5 • 20 years ago

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.

	Wayne Mery (:wsmwk)
	Comment 6 • 17 years ago

Dave, comment 0 is had to parse, but isn't summarized issue largely resolved by Bug 223523 Allow Keywords column to wrap.  Matthew I think is gone.

	Frédéric Buclin
	Comment 7 • 15 years ago

(In reply to comment #0)
> This means in "Change Columns" we should be able to specify which keywords
> we're
> interested in

No, we are not going to list tens of keywords in that list. WONTFIX

	Matthew Tuck [:CodeMachine] Reporter
	Comment 8 • 15 years ago

At no stage did I suggest listing keywords.  These could easily be text fields like elsewhere for keywords.

I can see that nowadays there's a snazzy new two-part list that did not exist when this bug was filed, but there's no reason you couldn't add an independent two-part list to the right that wouldn't clutter the main one, which seems to be the concern.  The room is certainly there, so I can't see any UI issues.