GWT UX: Use of space on the changes table

[lucamilanesio]

Hi all,

I know I am talking about the old-GWT UX ... but on stable-2.14 is the default supported one, still :-)

See below:

Do we really want to waste an entire (quite wide) column for a field that is rarely used?

The assignee field isn't really a mandatory field, his place should be only on the details screen.

Can we get rid of it on the default changes table for stable-2.14?

What do you think?

Luca.

[Matthew Webber]

We expect to make use of Assignee when we move to 2.14, so I personally would like the option to have that column on the search result screen, as illustrated.

It doesn't need to be there by default, though. I could be a user preference, like we already have for e.g. "Show Change Number In Changes Table".

Matthew

On Thursday, April 6, 2017 at 8:15:45 AM UTC+1, lucamilanesio wrote:

... 

[Sven Selberg]

Hi,

That's easy enough.

Just opt out of assignee workflow in your gerrit.config :-)

/Sven

----------- 8>< ------------------

[change]

    ...

    showAssignee = false

    ...

---------- ><8 -------------------

[Luca Milanesio]

Cool,

just proposed to have a backward-compatible UX by turning it to false by default:

https://gerrit-review.googlesource.com/102534

Luca.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.