pedroms

I'm a Product Designer at GitLab and I appreciate your feedback.

We are well aware of the advantages that Gerrit has over GitLab and how these are emphasized when teams migrate to GitLab. We are working on improvements that will help mitigate this. Specifically, targeting your points:

1. We're discussing ability to comment on commit messages: https://gitlab.com/gitlab-org/gitlab/-/issues/19691 2. From version 13.2 you can opt to show one file at a time, in your user preferences: https://gitlab.com/gitlab-org/gitlab/-/issues/222790. We have also listed a number of improvements to this feature in https://gitlab.com/groups/gitlab-org/-/epics/516.

Could you expand on point 3.b? If the commented line hasn't changed from version A to B, you should be seeing the comment in version B. Or maybe you're referring to something else?

Yes, there's some reasoning behind the decision to remove snippet Content from search results. You can find the original discussion and decision in this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/199220

GitLab has a page comparing it to Atlassian Bitbucket: https://about.gitlab.com/devops-tools/bitbucket-vs-gitlab.ht... There are also other comparison pages with other DevOps tools linked from this list: https://about.gitlab.com/devops-tools/ Even though that content is managed and served by GitLab, if you feel there are inaccuracies or a tool missing, you can propose edits through various channels.

If that repo is one of your frequently visited projects, you'll be able to quickly access it through the “Projects” dropdown in the header. Does that help?

Hi Eduardo, I'm a UX Designer at GitLab working on issue boards. If you click on the issue title, it will open the issue in a new window. If you click somewhere else in the issue card, it will open the summary sidebar. But I agree with you that it can be confusing and not the best UX! To improve it, we are planning to redesign the sidebar so that you can see most (if not all) of the issue's information, removing the need to open the issue in a new window. You can track the discussion and designs in this epic: https://gitlab.com/groups/gitlab-org/-/epics/383#note_108940... Feel free to participate and share your thoughts.

I'd love to hear more about your painpoints with issue boards (and issues in general).

We are not neglecting the core of the product, we just have a lot of different priorities. We are hiring almost continuously to keep the development fast and healthy.

People have already created issues for the improvements you've listed. Upvote them to show your support or create new ones if these don't satisfy your needs:

- CI manual jobs ignore dependencies: https://gitlab.com/gitlab-org/gitlab-ce/issues/28396

- Start a discussion from a non-discussion comment: https://gitlab.com/gitlab-org/gitlab-ce/issues/30299

Re: your last point, I've pinged someone from our CI area to see if we already have an issue for that.

Thanks for logging UX issues, especially regressions. Can you please link to one of those issues so the UX team can take a look?

Before coming up with this proposal, they evaluated GitLab and Phabricator: https://wiki.gnome.org/Initiatives/DevelopmentInfrastructure...

What kind of pipeline information do you usually look for? The pipelines list is available from the project main navigation.

About web hooks, we've recently changed things a bit and consolidated some of the project settings. You can find those in Settings > Integrations.

Speed is one of our main priorities for GitLab this year. We've started Gitaly, a project dedicated to that: https://gitlab.com/gitlab-org/gitaly

We expect it to become a standard component of GitLab in Q1 2017 and to reach full scope in Q3 2017.

This is something that has been on our minds for a while, and we must do it better. We created an issue for a smart project dashboard that aims to provide a better solution, it would be great to have your input there: https://gitlab.com/gitlab-org/gitlab-ce/issues/27112

You are right, GitLab doesn't have a polished UX. Improving that is one of our main objectives for the next two months: https://about.gitlab.com/handbook/ux/strategy/

If you are curious about what we're doing, take a look at the issues under UI Polish: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

Or feel free to point out any particular concerns here or through the issue tracker: https://gitlab.com/gitlab-org/gitlab-ce/issues