Branch permission to create (but not update) branches

Issue #15220 open
Cori Drew
created an issue

Summary: My (developer, non-admin) team needs the ability to create and merge (after getting PR approvals) release/ & hotfix/ branches. My team should not be able to push directly to develop, master, hotfix/ or release/ branches.

According to the documentation, that should not be a problem.

I think there's a bug.
Here's why:

According to this documentation, Branch Permissions should not prevent users from creating a branch:

Screen Shot 2017-11-15 at 8.17.59 AM.png

Repository write permissions exist for the group we need this functionality for:

Screen Shot 2017-11-15 at 9.19.50 AM.png

This describes exactly what we need:

Screen Shot 2017-11-15 at 2.28.49 PM.png

But when we set it to that, we can no longer create a branch:

(yes I'd normally create a hotfix from master, but this was a test)
Screen Shot 2017-11-15 at 9.27.39 AM.png

Please help. For auditing purposes, it is very important that no one can accidentally push to these branches directly.

Thanks in advance!!!

Official response

  • Alastair Wilkes staff

    Hi there,

    The documentation screenshots attached to this issue are from the Bitbucket Server documentation, which supports this use-case.

    Bitbucket Cloud (bitbucket.org) does not yet support this use-case. The current behavior is fine for long-running branches (e.g. master or production etc.) - you can create the long-running branch and then add the branch permissions - but this doesn't work for patterns like release/* where you need to be able to create branches that can't be pushed to. As a result, I'm converting this to a feature request to be prioritized.

    Thanks,
    Alastair
    Bitbucket PM

Comments (9)

  1. Alastair Wilkes staff

    Hi there,

    The documentation screenshots attached to this issue are from the Bitbucket Server documentation, which supports this use-case.

    Bitbucket Cloud (bitbucket.org) does not yet support this use-case. The current behavior is fine for long-running branches (e.g. master or production etc.) - you can create the long-running branch and then add the branch permissions - but this doesn't work for patterns like release/* where you need to be able to create branches that can't be pushed to. As a result, I'm converting this to a feature request to be prioritized.

    Thanks,
    Alastair
    Bitbucket PM

  2. Paul Vu

    This is blocking our dev team from creating a release branch in Bitbucket Cloud. We currently only allow merges via pull request and don't allow direct writes to the release branch. Not sure why a user now needs Write access to create a branch. This wildcard option had been working fine before...

  3. Log in to comment