Status Update
Comments
jr...@google.com <jr...@google.com> #2
[Empty comment from Monorail migration]
jr...@google.com <jr...@google.com> #3
Marked restrict-view-google because of screenshots and URLs for internal projects.
lo...@google.com <lo...@google.com> #4
[Empty comment from Monorail migration]
lo...@google.com <lo...@google.com> #5
[Empty comment from Monorail migration]
lo...@google.com <lo...@google.com> #6
I think we should come up with a stopgap solution for this before the June 4 deadline when we remove the option of using the GWT UI from googlesource.com .
Arnab, you've said you wanted to plan an incremental approach to the layout changes you're working on. This seems like one good area to focus on in the immediate term.
Arnab, you've said you wanted to plan an incremental approach to the layout changes you're working on. This seems like one good area to focus on in the immediate term.
ar...@google.com <ar...@google.com> #7
Yes Logan, that makes sense.
ka...@google.com <ka...@google.com> #8
[Empty comment from Monorail migration]
lo...@google.com <lo...@google.com> #9
[Empty comment from Monorail migration]
lo...@google.com <lo...@google.com> #10
[Empty comment from Monorail migration]
ka...@google.com <ka...@google.com> #11
[Empty comment from Monorail migration]
ka...@google.com <ka...@google.com> #12
[Empty comment from Monorail migration]
ka...@google.com <ka...@google.com> #13
[Description Changed]
ka...@google.com <ka...@google.com> #14
Removing RVG as this issue has had quite a bit of traffic and the scrubbed description is adequate for the issue.
ka...@google.com <ka...@google.com> #15
[Empty comment from Monorail migration]
da...@google.com <da...@google.com> #16
This is a really frustrating UX—so frustrating I continually switch back away from PolyGerrit despite the insistent “This UI is going away“ modal dialogs.
ka...@google.com <ka...@google.com> #17
[Empty comment from Monorail migration]
ka...@google.com <ka...@google.com> #19
For those interested -- the plan here is to replace the existing label display and submit requirement section with chips that have hovercards. This takes up significantly less vertical space, and also makes the UI more useful at-a-glance.
th...@yahoo.com <th...@yahoo.com> #20
Will that work in mobile and tablets?
wy...@google.com <wy...@google.com> #22
[Empty comment from Monorail migration]
wy...@google.com <wy...@google.com> #23
[Empty comment from Monorail migration]
ka...@google.com <ka...@google.com> #24
We've had to roll back this solution due to https://crbug.com/gerrit/9283 .
I've implemented a slightly different fix that uses screen real-estate slightly better on medium-to-small screens [1] [2] -- I'd love to hear if this UX has made life a bit easier for this specific pain point.
[1] Change:https://gerrit-review.googlesource.com/c/gerrit/+/184930
[2] Demo:https://imgur.com/a/AGxSpXG
I've implemented a slightly different fix that uses screen real-estate slightly better on medium-to-small screens [1] [2] -- I'd love to hear if this UX has made life a bit easier for this specific pain point.
[1] Change:
[2] Demo:
ka...@google.com <ka...@google.com> #25
Ping! Would love some feedback on Gerrit's current state.
sg...@google.com <sg...@google.com> #26
It's a clear improvement! For our 14-label project I can now see the first changed file without scrolling. I would like to see more changes in this same vein, though, as it's not yet as usable as the old UI and still has a ton of whitespace
eu...@google.com <eu...@google.com> #27
Same exact sentiment on my part(looking back at ag/4281895) - seems much more compact now which is great, though still not quite at the level as it was in the old UI
wy...@google.com <wy...@google.com> #28
[Empty comment from Monorail migration]
ka...@google.com <ka...@google.com> #29
Hi all,
Please have a look at these mocks! Notably, we've:
- Modified the label and submit requirements layout to be more dense (already live)
- Removed all information in the "Change metadata" section (above the labels) not pertinent to accounts (reviewers, assignee, owner, etc etc)
- Placed that information in a bar right below the change number/status/title to allow it to better occupy horizontal space
How do you all feel about these changes? Any and all feedback is appreciated!
Please have a look at these mocks! Notably, we've:
- Modified the label and submit requirements layout to be more dense (already live)
- Removed all information in the "Change metadata" section (above the labels) not pertinent to accounts (reviewers, assignee, owner, etc etc)
- Placed that information in a bar right below the change number/status/title to allow it to better occupy horizontal space
How do you all feel about these changes? Any and all feedback is appreciated!
ka...@google.com <ka...@google.com> #30
Also of note: any bits of information you see left out of these mocks (strategy, for instance) is _not_ going away in the actual UI -- it's just left out of these specific mocks.
sg...@google.com <sg...@google.com> #31
I support these changes
th...@yahoo.com <th...@yahoo.com> #32
I also support those changes, they look really nice!
ma...@gmail.com <ma...@gmail.com> #33
+1, these changes looks nice.
Took me a while to understand that the strange link "am-<UUID>" appearing in image #3 is actually the topic you added in the step before.
Took me a while to understand that the strange link "am-<UUID>" appearing in image #3 is actually the topic you added in the step before.
[Deleted User] <[Deleted User]> #34
[Comment Deleted]
da...@gmail.com <da...@gmail.com> #35
The https://crbug.com/gerrit/9723 may be related for the re-design of the change screen. The question is where the signed push verification result icon should be shown?
sh...@gmail.com <sh...@gmail.com> #37
Hi folks, we recently switched to 2.16.27 (previously on 2.10!) but don't see the UI changes mentioned here. Could you please point me to the version which has this fix?
is...@google.com <is...@google.com> #38
Edits were made to reflect the following in Monorail: auto-CCs.
oo...@gmail.com <oo...@gmail.com> #39
Supposed.org
Description
Affected Version:
What steps will reproduce the problem?
<scrubbed>
What is the expected output?
Dashboard with pending/incoming/submitted changes
What do you see instead?
no immediate issue.
Please provide any additional information below.
Problems start when going to a particular change.
See gerrit.png (old ui) and gerrit_new.png (new ui) for explicit differences.
What jumps first is the shear unreadability of the new ui.
It's divided into three columns, with inefficient use of space. The right column has way too many entries, with a "Show more button".
The left column takes way too much space to display the reviewer and approval information.
The center column is more than 70% blank, and that's for a descriptive changelist. A "Fix Build" patch will contain one line.
The MAIN issue is that from this view, I don't see the files. I have to scroll down which is a terrible design, since files is the most important part of a changelist. It makes any patch much less obvious and confusing.
Other things are cosmetic, e.g text seems to take twice as much space, at the minimum I would expect parameters similar to gmail (default/comfortable/compact), which I guess takes time to get used to.