306978 - Include date status whiteboard was last updated as a buglist column

Status: RESOLVED WONTFIX

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

Description

[Joel Peshkin]

Users want to include the data on which a bug's status whiteboard was updated
along with that status in buglists.

Comment 1

[Joel Peshkin]

Attachment: v1 - add the column

Comment 2

[Dave Miller [:justdave]]

I like the concept but this is kind of heading down a slippery slope...  before
long we'll want this on every column, and probably who made the last change to
that column, too.  Then again, that's probably not a bad idea, but it'd need a
really creative UI...

Comment 3

[Joel Peshkin]

Well....  in principle, we could let the user optionally edit the COLUMNLIST
cookie in a text box.   If we change its format to something that can be split
unambiguously (csv?), then we can continue to expand the format.

fieldname - what we have now
fieldname/t - the time fieldname was changed
fieldname/w - who changed fieldname
fieldname/"%24s" - specifying the width
fieldname/t"%Y:%m" - specify a format for the field
\n - start a new table row

If a user used the basic interface and set a columnlist, then switched to the
advanced, the list would just be a list of fielnames.

If a user user the advanced edit and then switched to the basic view, we would
want to have a warning that changing the list would cause loss of information.

Comment 4

[Marc Schumann [:Wurblzap]]

Comment on attachment 194783 [details] [diff] [review]
v1 - add the column

Removing r? per comment 2. Dave, please respond to comment 3.

Comment 5

[Frédéric Buclin]

We are freezing the code for 3.0 in two weeks and we don't expect this bug to be fixed on time.

Comment 6

[Max Kanat-Alexander]

Yeah, I agree, this is a slippery slope. If we can generalize this requirement somehow (that is, say "people want to know about when X changed"), and there is sufficient visible demand for that generalized feature, then perhaps we can consider some form of generic implementation. But I think adding it just for one field is too much complexity without enough value, at this point.