New issue
Advanced search Search tips

Issue 647396 link

Starred by 1 user
Status: Duplicate
Merged: issue 639396
Owner: ----
Closed: Oct 2016
Cc:
seanmccullough@chromium.org
martiniss@chromium.org
zhangtiff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

SOM bugs should have more information

Project Member Reported by martiniss@chromium.org, Sep 15 2016 
Specifically, they should show if they're closed, status, owner. Maybe some labels as well? 

This would require caching this data on the go backend, which should be fine I think. Could do this asynchronously on the frontend (display the number, trigger a request to the backend, show data from monorail when the backend sends it back).

Comment 1 by seanmccullough@google.com, Sep 15 2016

Cc: zhangtiff@chromium.org martiniss@chromium.org seanmccullough@chromium.org

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

Labels: -Milestone-SoMNGFollowUp Milestone-UX

Comment 3 by zhangtiff@chromium.org, Oct 20 2016 

Was this suggestion meant to be for the bug queue or for linked bugs?

Comment 4 by seanmccullough@google.com, Oct 20 2016 

I think this was for linked bugs. We show very little info about those (compared to bugs in the bug queue), but it would be good to have more info in the bug queue as well.

Note that bugs can contain Restrict-View-Google labels, which mean they should be hidden from non-googlers. IIRC we only allow googlers to see SoM at the moment, so it's not an immediate problem but we should keep that visibility restriction in mind.

Comment 5 by zhangtiff@chromium.org, Oct 20 2016

Mergedinto: 639396
Status: Duplicate (was: Available)
►

Sign in to add a comment