The way I implemented this at my previous job was by adding tasks to the pull request that the reviewers had to check off before approving the request (I used scriptrunner to do this) and the merge policy to not allow the merge to happen until all tasks were checked. I know this does not prevent the author of the request to check the tasks off, but we could always hold the reviewers and authors accountable if during a review we found that they had not followed the approval process.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events