5 ms·

> complete usability mess Works fine for us at zenAud.io... anything in particular you find lacking? I must admit though: their change to group-based issues a

> complete usability mess Works fine for us at zenAud.io... anything in particular you find lacking? I must admit though: their change to group-based issues annoys me because you have to jump through a bunch of links to get to the milestones for a project. But otherwise it's pretty similar to competitors... but hey, maybe we're not real power users.

yurishimo 8y ago
Unrelated, but your home page has some horizontal scrolling. 2015 MBPro/Firefox Dev Edition
- seertaak 8y ago
  Urgh.... thanks for pointing out. This is what happens when a C++ dev creates a website! UPDATE: temporary fix -- I removed the offending section.
- roninb 8y ago
  Weird way to try to discredit someone...(?) Works fine on my 2017 XPS 15/Firefox Quantum.
  - detaro 8y ago
    How do you get the idea that pointing out a bug with a site is an attempt to discredit and not common courtesy among fellow community members, especially after the site owner has already thanked them and fixed the issue?
Karunamon 8y ago
Most of the issues I have with Gitlab's UI are the result of many small, seemingly insignificant and probably nitpicky-sounding choices that tend to build on to one another. All of these are my humble opinion: * Everything about browsing projects. Okay, so if you click on "Projects", you get taken to a list of "your projects". That's kind of annoying since I'd go to my personal page if I wanted a list of stuff I've touched (kinda like Github) but it's defensible as a choice. If you want something that isn't yours, it takes another click to "explore projects", which goes to a "trending" page that will either be blank or have very few things on it, and another click after that to get to the time-sorted list of everything based on last update, which is usually what I want. * Groups appear to be second class citizens of sorts, rather than the top level organizers they really are. (I.e. groups are separate from projects, even though all projects live in a group or user space). Bitbucket did this better - when you log in, you see a list of groups first, and from there drill down into projects. Basically, it kinda wants to be a hierarchy but offers too many ways to circumvent it. Imagine if you were just browsing a file explorer and saw files two levels below your pwd. It's disorienting. * Top level project pages feel cluttered and noisy. Github does this better, without requiring a separate sidebar. * Repo settings are buried under expand links. This did not make the page more usable, it made it so I had to guess where the setting I want is. * Why are there two nearly identical pages for showing repository contents? (One at the top level of a project, which is any project's landing page, and another on its "repository" tab, which is the same view missing a few elements) * Releases and their artifacts are buried behind "tags" (which they technically are in Git parlance, but still) or a very easy to overlook CI status badge on the last commit shown on the landing page. Releases can only be created with API calls or manually through the new tag page, rather than programmatically or as part of a CI job. (Yes, I know, the CI job could technically call the API. You get a cookie. Point is, it feels rather buried.) * Build artifacts can only be downloaded in a zip bundle, rather than individually * I haven't figured out how to turn off the "Do you want to enable Auto DevOps?" div showing in every single repo. * Advertising for Google Cloud on the CI Kubernetes page is just plain tacky. I'm sure there's a way to turn this off, but I shouldn't have to in the paid Enterprise product.
- themacguffinman 8y ago
  Yes! GitLab gets a hundred little things wrong in the web interface. It really seems like they're trying to win on features when user-friendliness should be their #1 priority especially if they want to take GitHub's crown of "code hosting for everyone". This is a screenshot of their issue page taken straight from their website: https://about.gitlab.com/images/feature_page/screenshots/41-issue-due-dates.png https://about.gitlab.com/images/feature_page/screenshots/41-... It's just cluttered. All the controls you need are there, but it's not focused or simple. My eyes don't know where to focus. Another example: https://about.gitlab.com/images/feature_page/screenshots/34-burndown-charts.png https://about.gitlab.com/images/feature_page/screenshots/34-... Things are just thrown on the page.
- nameiscubanpete 8y ago
  Just to note, you can indeed browse build artifacts on GitLab, but finding it is a PITA. You have to drill into your CI Job and there's a button link on the right. It'd be nice to have a "Browse artifacts" option in the Download widget.
- svesselov 8y ago
  This isn't nitpicky at all @Karunamon, this is UX gold! I have created issues for some of your major points here, I would love to get further input from you as we work through them. https://gitlab.com/gitlab-org/gitlab-ce/issues/47400 https://gitlab.com/gitlab-org/gitlab-ce/issues/47400 https://gitlab.com/gitlab-org/gitlab-ce/issues/47401 https://gitlab.com/gitlab-org/gitlab-ce/issues/47401 https://gitlab.com/gitlab-org/gitlab-ce/issues/47402 https://gitlab.com/gitlab-org/gitlab-ce/issues/47402 We have a couple of issues open to address downloading individual files/artifacts. https://gitlab.com/gitlab-org/gitlab-ce/issues/24704 https://gitlab.com/gitlab-org/gitlab-ce/issues/24704 https://gitlab.com/gitlab-org/gitlab-ce/issues/23705 https://gitlab.com/gitlab-org/gitlab-ce/issues/23705 I am going to add your feedback on both of those and see if we can get some attention in this area. These may seem like small, insignificant problems but they can easily roll up into larger UX issue. Keep these insights coming!
- matejlatin 8y ago
  This is really useful feedback @Karunamon! I see Sarrah already addressed it so I just wanted to add my bit: I also think that the approach we used for designing settings pages isn't optimal and suggested improvements in a discussion on a related issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/45219 https://gitlab.com/gitlab-org/gitlab-ce/issues/45219 After seeing your feedback (and confirming my assumption) I decided to open a new issue to specifically address this and would love to get your feedback on the proposed solution: https://gitlab.com/gitlab-org/gitlab-ce/issues/47405 https://gitlab.com/gitlab-org/gitlab-ce/issues/47405 Thanks again for taking the time to write such detailed feedback down. It's really helpful to us. Cheers!

yurishimo 8y ago

Unrelated, but your home page has some horizontal scrolling. 2015 MBPro/Firefox Dev Edition

seertaak 8y ago
Urgh.... thanks for pointing out. This is what happens when a C++ dev creates a website! UPDATE: temporary fix -- I removed the offending section.
roninb 8y ago
Weird way to try to discredit someone...(?) Works fine on my 2017 XPS 15/Firefox Quantum.
- detaro 8y ago
  How do you get the idea that pointing out a bug with a site is an attempt to discredit and not common courtesy among fellow community members, especially after the site owner has already thanked them and fixed the issue?

Karunamon 8y ago

Most of the issues I have with Gitlab's UI are the result of many small, seemingly insignificant and probably nitpicky-sounding choices that tend to build on to one another. All of these are my humble opinion: * Everything about browsing projects. Okay, so if you click on "Projects", you get taken to a list of "your projects". That's kind of annoying since I'd go to my personal page if I wanted a list of stuff I've touched (kinda like Github) but it's defensible as a choice. If you want something that isn't yours, it takes another click to "explore projects", which goes to a "trending" page that will either be blank or have very few things on it, and another click after that to get to the time-sorted list of everything based on last update, which is usually what I want. * Groups appear to be second class citizens of sorts, rather than the top level organizers they really are. (I.e. groups are separate from projects, even though all projects live in a group or user space). Bitbucket did this better - when you log in, you see a list of groups first, and from there drill down into projects. Basically, it kinda wants to be a hierarchy but offers too many ways to circumvent it. Imagine if you were just browsing a file explorer and saw files two levels below your pwd. It's disorienting. * Top level project pages feel cluttered and noisy. Github does this better, without requiring a separate sidebar. * Repo settings are buried under expand links. This did not make the page more usable, it made it so I had to guess where the setting I want is. * Why are there two nearly identical pages for showing repository contents? (One at the top level of a project, which is any project's landing page, and another on its "repository" tab, which is the same view missing a few elements) * Releases and their artifacts are buried behind "tags" (which they technically are in Git parlance, but still) or a very easy to overlook CI status badge on the last commit shown on the landing page. Releases can only be created with API calls or manually through the new tag page, rather than programmatically or as part of a CI job. (Yes, I know, the CI job could technically call the API. You get a cookie. Point is, it feels rather buried.) * Build artifacts can only be downloaded in a zip bundle, rather than individually * I haven't figured out how to turn off the "Do you want to enable Auto DevOps?" div showing in every single repo. * Advertising for Google Cloud on the CI Kubernetes page is just plain tacky. I'm sure there's a way to turn this off, but I shouldn't have to in the paid Enterprise product.

themacguffinman 8y ago
Yes! GitLab gets a hundred little things wrong in the web interface. It really seems like they're trying to win on features when user-friendliness should be their #1 priority especially if they want to take GitHub's crown of "code hosting for everyone". This is a screenshot of their issue page taken straight from their website: https://about.gitlab.com/images/feature_page/screenshots/41-issue-due-dates.png https://about.gitlab.com/images/feature_page/screenshots/41-... It's just cluttered. All the controls you need are there, but it's not focused or simple. My eyes don't know where to focus. Another example: https://about.gitlab.com/images/feature_page/screenshots/34-burndown-charts.png https://about.gitlab.com/images/feature_page/screenshots/34-... Things are just thrown on the page.
nameiscubanpete 8y ago
Just to note, you can indeed browse build artifacts on GitLab, but finding it is a PITA. You have to drill into your CI Job and there's a button link on the right. It'd be nice to have a "Browse artifacts" option in the Download widget.
svesselov 8y ago
This isn't nitpicky at all @Karunamon, this is UX gold! I have created issues for some of your major points here, I would love to get further input from you as we work through them. https://gitlab.com/gitlab-org/gitlab-ce/issues/47400 https://gitlab.com/gitlab-org/gitlab-ce/issues/47400 https://gitlab.com/gitlab-org/gitlab-ce/issues/47401 https://gitlab.com/gitlab-org/gitlab-ce/issues/47401 https://gitlab.com/gitlab-org/gitlab-ce/issues/47402 https://gitlab.com/gitlab-org/gitlab-ce/issues/47402 We have a couple of issues open to address downloading individual files/artifacts. https://gitlab.com/gitlab-org/gitlab-ce/issues/24704 https://gitlab.com/gitlab-org/gitlab-ce/issues/24704 https://gitlab.com/gitlab-org/gitlab-ce/issues/23705 https://gitlab.com/gitlab-org/gitlab-ce/issues/23705 I am going to add your feedback on both of those and see if we can get some attention in this area. These may seem like small, insignificant problems but they can easily roll up into larger UX issue. Keep these insights coming!
matejlatin 8y ago
This is really useful feedback @Karunamon! I see Sarrah already addressed it so I just wanted to add my bit: I also think that the approach we used for designing settings pages isn't optimal and suggested improvements in a discussion on a related issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/45219 https://gitlab.com/gitlab-org/gitlab-ce/issues/45219 After seeing your feedback (and confirming my assumption) I decided to open a new issue to specifically address this and would love to get your feedback on the proposed solution: https://gitlab.com/gitlab-org/gitlab-ce/issues/47405 https://gitlab.com/gitlab-org/gitlab-ce/issues/47405 Thanks again for taking the time to write such detailed feedback down. It's really helpful to us. Cheers!