Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,080
Community Members
 
Community Events
176
Community Groups

Is there a way to configure Required Approvers for a Pull Request?

Is there a way to configure Required Approvers for a Pull Request?

For example, our team wants us to have at least one person from the Required Approvers list approve a Pull Request before it can be merged. 

1 answer

1 accepted

2 votes
Answer accepted

Hi Cole!

Here are a few solutions;

1. In your Bitbucket Repository settings, you can create "Default Reviewers" on the left.

Then under "Branch Permissions" you can select "Check for at least N approval from  default reviewers".

This will get you close, but not quite to the result you are after.

Screen Shot 2022-07-19 at 11.40.55 am.png

 

2. You can sign up for bitbucket premium to block merge if N approvals from default reviewers have not been reached. 

- You will need to change every bitbucket branch setting if a default reviewer leaves or you want to add a new one. 

 

3. Our product Workzone for Bitbucket will offer all of the above + more:

- Workzone will allow you to introduce reviewer groups, group quota and merge-control. 

- You can set up a default reviewer group, so you only need to change the group members and Workzone will apply that automatically.

 

Happy coding!

Sean 

Technical Support at Izymes

Hi Sean, 

Thanks for your response! 

For Options 1 and 2 I don't believe our version of BitBucket (Atlassian Bitbucket v7.17.5) supports those configurations. 

In regards to Option 3, we're using Workzone 7.5.1. I was able to successfully configure Mandatory Users. However, the Pull Request Merge Check is all of those users to Approve. Is there a way where we can allow a specific number or ratio of those in the Mandatory Users list to Approve? 

Thanks, Cole

Hi Cole, 

If you head to your repository settings > "Workzone" (under "Add-Ons") > "Merge" tab. 

You can then edit the existing merge configuration you have set up or create one. 

This will allow you to create a Boolean Expression based merge condition under the "Advanced" tab as seen in the screenshot below. This should solve your dilemma.

It may also help to refer to our new documentation space here.

Let me know how that goes & if we can help with anything else.

Best, Sean

Screen Shot 2022-07-21 at 2.08.50 pm.png

Like Cole Orton likes this

That worked! 

Thanks for your help on this. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events