[suchar]

Yup, it's "funny" that even basic functionality doesn't work as expected: https://gitlab.com/gitlab-org/gitlab/-/issues/350662

I encounter this issue pretty often and it makes code review experience miserable. It's not blocking any work, but it is frustrating enough that for any new project I would try to avoid using Gitlab

[yjftsjthsd-h]

And what a typical issue that is. Opened a year ago, initially some requests for internal clarification that went nowhere, plans to be fixed by an upcoming release, then loads of metadata and bot comments with minimal actual work happening, followed by pushing back the release they want to fix it in, followed by reducing its priority, deciding that actually they don't need to fix it and can just throw it on the backlog, more comments about users being affected, and then today a comment that it got brought up in a discussion here:)

[phikai]

Hey - I'm the PM for our Code Review group. Sorry to see you're running in to that issue, it's been a real challenge for us. If you're running in to it pretty often, it'd be great if you could provide some details on what steps you're taking (maybe even record a video) to help us figure out what's going on. For lots of bugs, the hardest thing for us to do is reproduce them... so if you've got a reliable way to do that, it really helps us prioritize things to fix.

[thunky]

> it'd be great if you could provide some details on what steps you're taking (maybe even record a video) to help us figure out what's going on

The comment you're replying to has a link to an issue which includes a video and a test project.