New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 4552 link

Starred by 5 users

Issue metadata

Status: Released
Owner:
Closed: Feb 2018
Cc:
Components:
ReleasedIn: 459.0



Sign in to add a comment

Dashboard column sizing is sub-optimal

Project Member Reported by jwer...@chromium.org, Sep 13 2016

Issue description

On my dashboard I have a list of CLs, one per row. Every row has different columns for Project, Branch, etc.

The Chromium OS project likes to use pretty big names for projects and branches, such as chromiumos/third_party/coreboot and firmware-gru-8785.B. Unfortunately, with the available column size on my 1280x800 laptop, all I'm seeing in every column is stuff like chromiumos/third... and firmware-gr...

Of course there's no perfect solution here and some stuff will have to be truncated no matter how you design it. However, for the Chromium OS use case (and I'd bet for most others), truncating the front of the field is much more likely to preserve the most useful/distinct part than truncating the tail. I'd much rather see columns with ...arty/coreboot and ...gru-8785.B than the other way around, because I probably know the prefix from context anyway.
 
Project Member

Comment 1 by andyb...@chromium.org, Sep 13 2016

Labels: Priority-3 Hotlist-Chromium
Status: Accepted (was: New)
Project Member

Comment 2 by andyb...@chromium.org, Oct 5 2016

Labels: Milestone-Chromium-Afterglow Hotlist-Dashboard
I'm not sure if this was intentional or accidental, but behavior seems to have changed quite a bit here... see attached screenshot for the current situation. Now the Project and Branch row seem to always expand to allow the longest value in the displayed table to be printed in full, which is even more undesirable because some project and branch names are really long. This can have some pretty ridiculous effects like cutting the subject line down to less than 25 chars and still making the whole table to wide to fit (notice the horizontal scrollbar).

I think the column sizing really needs to be overhauled completely with some more focus on what the user likely wants to see. Columns should only expand to the maximum size when they have some very well-known to be limited values (e.g. dates, diff sizes, checkmarks). After those the remaining space should be divided into ratios depending on how important each column is... e.g. Subject should likely get the most real estate (at least 30% screen width?) and the others should get lower allotments accordingly. Every column should get the right default as to which part is truncated if the width is insufficient (as I argued above I think Project and Branch ought to truncate the front, whereas Subject should probably continue to truncate the end). For some columns like Status it might also help to introduce abbreviations to save space (e.g. "Merge Conflict" = "MC").
polygerrit_dashboard_bad_column_sizing.png
536 KB View Download

Comment 4 by derat@chromium.org, Jul 31 2017

Cc: derat@chromium.org
Summary: Dashboard column sizing is sub-optimal (was: Dashboard columns should truncate front, not tail, of CL fields)
I was about to file the same issue. Also note that author fields aren't truncated, which can result in a huge amount of space being devoted to out-of-office messages.
Screenshot 2017-07-31 at 07.21.21.png
150 KB View Download
Project Member

Comment 5 by kaspern@google.com, Aug 14 2017

smoreland@ has also proposed the idea of having the columns be reorderable, which would allow users to prioritize certain information.


Project Member

Comment 6 by kaspern@google.com, Jan 20 2018

Labels: Triaged-Undecided
Moving this to the triage queue.
Project Member

Comment 7 by wyatta@google.com, Jan 22 2018

Labels: UX-Incoming
See also internal issue b/64145900
Project Member

Comment 8 by wyatta@google.com, Jan 22 2018

Labels: -Triaged-Undecided Triaged-Yes
Project Member

Comment 9 by kaspern@google.com, Jan 22 2018

Cc: nsanders@chromium.org
 Issue 8198  has been merged into this issue.
Project Member

Comment 10 by beckysiegel@google.com, Feb 1 2018

Labels: -UX-Incoming UX-Current
Project Member

Comment 11 by logan@google.com, Feb 1 2018

 Issue 8165  has been merged into this issue.
Project Member

Comment 12 by kaspern@google.com, Feb 12 2018

Labels: -UX-Current UX-Incoming
Project Member

Comment 13 by wyatta@google.com, Feb 12 2018

 Issue 8313  has been merged into this issue.
Project Member

Comment 14 by kaspern@google.com, Feb 14 2018

Labels: -Priority-3 Priority-2
Owner: kaspern@google.com
Author and branch columns should be truncated at a reasonable max-width.
Project Member

Comment 15 by beckysiegel@google.com, Feb 14 2018

Labels: -UX-Incoming UX-Current
Project Member

Comment 16 by kaspern@google.com, Feb 16 2018

Labels: -UX-Current
Status: Submitted (was: Accepted)
Project Member

Comment 17 by wyatta@google.com, Feb 20 2018

ReleasedIn: 459.0
Project Member

Comment 18 by wyatta@google.com, Feb 20 2018

Status: Released (was: Submitted)
Labels: FixedIn-2.15.2
Project Member

Comment 20 by luca.mil...@gmail.com, Nov 20

Labels: FixedIn-2.16

Sign in to add a comment