101875 - component column should be after product column in query results

Status: RESOLVED FIXED

(Bugzilla :: Query/Bug List, defect, P4)

Description

[Paul Baker]

If you have the Component and Product columns turned on in the bug query results
listing, the Component column comes before the Product column.

This seems counter-intuitive to me since Products contain Components, not the
other way around.

If you have a list of bugs with many product/component combinations and you are
visually scanning through looking for bugs for a particular product/component
your eyes have to follow down the Product column...then move left to check the
Component column. This causes a visual flow problem since most everyone reads
from left to right, not right to left. Hope I haven't over explained the problem :-)

Comment 1

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 2

[Paul Baker]

Attachment: patch to colchange.cgi to swap product/component order

This puts the Product column before the Component column in the buglists.

Comment 3

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

Comment on attachment 59234 [details] [diff] [review]
patch to colchange.cgi to swap product/component order

Works, r=myk, no second review needed.

Comment 4

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

Reassigning to patch author.

Comment 5

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

Low risk.  Checking in.

Checking in colchange.cgi;
/cvsroot/mozilla/webtools/bugzilla/colchange.cgi,v  <--  colchange.cgi
new revision: 1.19; previous revision: 1.18
done

Comment 6

[Jonas Jørgensen]

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