We agree here as well. It would be best if the developer could simply initiate the review and then the PM (moderator in our case) or any Project "Owner" goes in and assigns reviewers. I've had so many questions from developers, "So who should I pick?" And that is because, a developer (especially junior) doesn't know who is most experienced and who is too busy.

We use a similar process here. Please consider support it.

Same process with our team. We don't require specific people to do a review. It is handled by whichever dev is available. It would be great to create the review with no reviewer selected and have it visible to all team members. A button for another dev to 'claim' it would provide a very efficient workflow.

I completely agree. We have "Code Review" as a column on our sprint board and the first available developer that needs a new task are required to address code reviews first. This would require the possibility to "take" a review and accept it, making that developer the current reviewer of the code review. This way of assigning the reviewers at the moment the code review is requested feels backwards and not really agile at all.

Definitely. The process on our team is that a work item goes up for review and the next two people who become available review it. It is frustrating for them to either have to go talk to the review creator to be added, or to have the review creator add every single team member just so the two who end up reviewing it can do so.