New issue
Advanced search Search tips

Issue 658781 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug


Participants' hotlists:
Tiff-List


Sign in to add a comment

Improve Sheriff-o-Matic alert UI

Project Member Reported by ojan@chromium.org, Oct 24 2016

Issue description

The UI has gotten hard to follow. Links and boxes that wrap in strange places, lack of clear delineation between sections, spaces where there shouldn't be spaces, etc.

Might be worth spending some time polishing and just making it easier to see what's happening on the page. Attaching a screenshot that shows a bunch of issues.
 
Screenshot 2016-10-24 at 10.51.22 AM.png
711 KB View Download
Cc: zhangtiff@chromium.org
Labels: Milestone-UX
Status: Available (was: Untriaged)
We have a Chrome UX + Infra meeting with helenharris@ scheduled for 11/29. This might be a good issue to discuss if we have time (PolyGerrit is sharing this slot with us, so we won't get the entire meeting for SoM).


Owner: zhangtiff@chromium.org
I agree that the UX has gotten kind of cluttered feeling. It is a bit difficult to keep the alerts information dense and have things still visually appealing. 

I can play around a bit to see what I can fix, but opinions from a UX expert would be great. :) 
Cc: seanmccullough@chromium.org
I feel like to perhaps we should try to establish a clearer hierarchy of information for alerts on Sheriff-o-Matic. 

Emphasize things sheriffs look for more while de-emphasizing things that are more side information/extra context. I think a lot of the clutter comes from the fact that the alerts have a lot of different information that is competing for the sheriff's attention at the same level. 

Perhaps some of the responses from the survey we're currently sending out might help provide some insights into what sheriffs tend to prioritize here. 

I will think on this some and probably later propose a few mockups for adjusted alert UIs. 

Comment 4 by benhenry@google.com, Dec 19 2016

Status: Assigned (was: Available)
There is an owner on this bug, but the status was not "Assigned" or "Started". Fixing. If you do not own this bug, please remove yourself as the owner and make the status "Available".
I was digging through old infra docs out of curiosity and found these notes that the maker of the Rietveld Polymer UI left for the Polygerrit team on design: https://docs.google.com/document/d/1-WUl8-HDimjYbKhDRMYYdw9ocbf5UaG9gJFWLpnJJv0/edit#heading=h.9smzxs4hvk1u 

I think it would be good to try to implement some of these tips for Sheriff-o-Matic to try to improve the design. 
This is a great doc! I believe esprehn works on our floor :)
https://bugs.chromium.org/p/chromium/issues/detail?id=712085#c4 - Linking this comment by hcarmona@ here because I think it contains some information that might be useful in doing a redesign of the alerts for Sheriff-o-Matic

"Most useful parts of the cards for me are:
  - builders that have failed
  - how many builds have failed
  - whether there are comments to look at or not
  - What CL does Findit think caused this

Parts that I wouldn't mind if they were collapsed:
  - bugs (a count w/ links similar to comments would be good)
  - tests that failed (these are already grouped)
  - regression range"

I also want to note that I've heard of mutters on IRC and such that Sheriff-o-Matic is often very confusing. I think this can definitely be helped by making sure we emphasize the things sheriffs look at the most. 

At some point I want to try to do some mockups for possible redesigns of alerts (with a focus on having good information hierarchy) and run them by some sheriffs. 
Summary: Improve Sheriff-o-Matic alert UI (was: sheriff-o-matic UI too cluttered)
Narrowing the scope of this bug because I think Sheriff-o-Matic as a whole is decently uncluttered looking now, but the alert UI could still stand to be improved. 
 Issue 737312  has been merged into this issue.
Labels: Milestone-Goodies

Sign in to add a comment