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:
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
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:
Sorry, didn't see your comment till now... About the last point - yes, there is a ticket about it (too lazy to find it now ;).
The first ticket is a bit different. Starting depending jobs automatically would be great, but I would be satisfied if I could just click a button "Start this job when dependencies finish".
But anyway, those are all quite old tickets and I know from talking with other developers that I am not the only one having a sore point. And I don't see much improvement in the last year or so.
Don't get me wrong - I still love the product and would like to see it get even better.
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?