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

Branch Permissions - Prevent creating new release branch without write access

In Bitbucket Server, restricting access to just change merged via pull request, still allowed users to create a new release branch (or whatever branch type was restricted) but in Bitbucket Cloud, that same restriction, prevents anyone from creating the branch, and they have to get write access to the branch, in order to create the branch. So if adding everyone, if that is what is wanted to create release branches, then there is almost no point to the restriction.

Is this a bug, or by design? And why the difference in function between Server and Cloud? Is there a good reason why Cloud restricts the creation of the branch?

1 answer

1 accepted

0 votes
Answer accepted

Hi Curtis,

I think that this was by design initially, Bitbucket Server and Bitbucket Cloud are different products and certain features work differently in each product.

We have a request to change this behavior in our issue tracker:

I would suggest adding your vote to that ticket (by selecting Vote for this issue link). You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

Another way to work around this at the moment would be by creating a branch permission with Write access:None for each release branch after creation, instead of using the release/* pattern.

Kind regards,

While not the answer I was hoping for, and for our group, that workaround would not be feasible, it is the answer.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events