Are branch permissions supposed to be additive?

[Administrator]

I've defined branch permissions for a specific branch at the project level as well as at the repository level.

I'm finding only the repo level is taking effect.

For example:

Project level: Prevent all changes except for Group X.
Repo level: Prevent all changes except for User A.

Expected: Group X and User A allowed to commit to the branch.

Actual: Only user A is allowed to commit to the branch.

[Julius Davies [bit-booster.com]]

Defining permissions at the "repo" level essentially turns off all project-level permissions for that repo.   It's a pure override, so you will need to copy/paste all the project-level permissions down into your repo-specific config if you want to keep them.

One workaround would be to use our free Control Freak add-on to use some of its branch permissions on top of the native Bitbucket mechanism.  Control Freak's permissions are additive when combined with the Bitbucket native mechanism.

(Control Freak's permissions ARE NOT additive against itself - it also implements an override mechanism, and again a repo override replaces the project config).

[Mohamed Adel]

@Administrator

This is a branch overlap permission, please read this article

[Administrator]

Thanks.  But this has nothing to do with the Project vs. Repo permissions.

It's also for the cloud version, not the server versions I'm running.