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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Default reviewers in BitBucket Cloud not working at all?

We've defined a set of default reviewers in our BitBucket Cloud repository.

However, it seems to have zero effect. Any time we create a PR from a fork, the list of reviewers is always empty and the list of default reviewers does not seem to get applied at all.

is this a bug or is there something else that needs to be set up?

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 11, 2018

Forks may start out with the same repository content as their upstream, but they don't automatically inherit permissions, default reviewers, merge checks, or other configuration details. (The general idea is that, if I fork a repo, then I get to decide how all the things work.) You'll need to populate the default reviewers (etc.) for each fork, either through the API or by hand.

(Branches are not subject to this, as they're still a part of the original repo.)

That is unexpeced...BitBucket on-prem does this *properly* (i.e. as expected).

This is clearly a bug in how BitBucket Cloud handles it vs. the on-prem server version.

Is there an ETA to fix this?

This makes it very hard to ensure quality and proper code reviews, especially if dealing with remote teams.

I also find this confusing and frustrating. The pull request is being created in the repository being merged into and not the fork. Why wouldn't default reviewers have an effect?

Adding to the issue I can't add default reviewers to my private fork unless I give access to the fork to all of the reviewers who already have access to the main repository. Effectively each user can only add themselves as a reviewer which is rather silly.

I can however add the users manually every time I create the pull request but the entire point of having default reviewers in the first place is to remove the need for doing this.

Did you find any solution on this? Its 2022 and I think default reviewer still not working. Thanks

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events