Issue rejection workflow

[Mehmet Perk]

I worked in around 10 different teams so far and the development workflow was usually similar, except the part where the person who accepts the user story rejects (not-accepts) it. What are the best practices here? How we currently do is the following:

1. User story lands to the 'user acceptance test' column.
2. The product manager reviews the story and goes through the acceptance criteria 1 by 1.
3. PM writes a comment with each criterion's status (X or ✓) and moves the issue back to To Do
4. Engineering lead checks the comment and aligns with the engineering team to re-create new sub-tasks.

I have a feeling that this is not so optimal and would like to hear your opinion. How is your 'rejection workflow?'