> If I told my manager it was his problem to get my code reviewed, he would tell me to do my job.

If that's how you interact with your team members, no wonder they refuse working with you.

What any competent developer does is a) update ticket to move it to review, b) call out the PR in whatever system you guys use, c) after a reasonable amount or time inform your scrum master/manager that your task is code-complete and is blocked by the review, d) update ticket with a notice that PR is still pending review. Go back to step b) and repeat until the PR is merged.

Done.

Updating the ticket and making a best effort to get the ticket moving is all that's expected from you. By design. That's how things are supposed to work. If your manager doesn't care, it's nothing they want to push anyway, as proven by the ticket history.

> no wonder they refuse working with you.

Weird and abrasive assumption you make.

> Updating the ticket and making a best effort to get the ticket moving is all that's expected from you.

I have never worked somewhere that ran things as you describe. But then everywhere I’ve ever worked has expected a high level of personal responsibility, not “best effort” that consists of a one time Slack message and tagging work as blocked.