I find the GitLab issue board to have a poor UX. For example, depending on where you click, it will open a small summary to the right or it will open a new page with all the issue information.

Also, it is ridiculously expensive to have epics, compared to every other issue tracker I have seen, in GitLab issues.

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).

Hi Eduardo, thanks for writing about your experience with GitLab Issue Boards.

Could you please tell us what could make your experience more convenient? Do you have an open issue regarding your suggestions? If not, it would be great if you could open an issue about it at https://gitlab.com/gitlab-org/gitlab-ce/issues. We'd like to follow up on it.

It’s really valuable for us when users take the time to submit issues for bugs, changes, or feature proposals. This helps us steer the product in the right direction.

Can I remove old docker images from the registry yet? Heck, I still can't order by date, which should have been the default all along. Why would anyone want to see the images ordered alphabetically?

It can take minutes to page through and find the most recent image buried among hundreds.

I'm sorry this has taken so long, but we are working on some foundational API's to manage and list images right now: https://gitlab.com/gitlab-org/gitlab-ce/issues/55978. I've also added your feedback on sorting, thank you!

We are also setting up a team to focus on just packaging related features within GitLab, like the Registry, which should improve our velocity in this area.

Thank you.

> focus on just packaging related features within GitLab

I'm curious what you mean by that?

We have established teams for each of our DevOps stages: https://about.gitlab.com/stages-devops-lifecycle/

Package encompasses both the Container Registry, as well as other repository types like Maven, NPM, etc.

Ah. So you mean "packaging-related features", not "packaging related features"?

Yes, I think Josh means that.