I'm on the community advocates team at GitLab and we really appreciate your feedback. I wanted to point out that our team responded to your post on the GitLab forum, you can see the response here: https://forum.gitlab.com/t/gitlab-support-is-no-longer-proce...
Thanks — I've been replying there but figured I should comment here since this is where I first saw it. I definitely hope this leads to some UX work, especially through the lens of thinking about how badly it will fail for vulnerable users.
Just want to take a second to point out the highlight post I added to the story about the release yesterday, for anyone who missed it: https://news.ycombinator.com/item?id=23917493
We do prioritize tickets that indicate an issue as complete blocker. Our team that monitors hackernews for feedback, issues, and criticisms work to make sure these things are actually being prioritized, as it’s not always clear from the support ticket how severe a blocker might be.
Yes, if the support ticket is opened when the issue is discovered. This particular instance was first reported on hackernews and was due to our dormant namespace policy: https://news.ycombinator.com/item?id=23827772