Permission to branching model hierarchy

[Rodrigo Olivares B2]

We use branching model and permissions with proyect level configuration.

We are trying to allow to developers only create and commit into branches like  "feature/ISSUE-CODE-..."

We are trying to acomplish that using, on project permissions:

• "*", nobody access
• "feature/*" write: developer-group, write with PR: anyone with access

Users in "developer-group" can't commit neither using console or bitbucket web.

How we can acomplish that?

NOTE: we've already applied this setup 

https://confluence.atlassian.com/bbkb/restrict-creation-of-branches-to-certain-patterns-1272283176.html

[Patrik S]

Hello @Rodrigo Olivares B2 ,

and welcome to the Community!

I wasn't able to reproduce the issue you are facing, as when I set the following branch restriction rules :

 

It allowed my user only to commit to branches matching the feature/*, while it was blocked for other types of branches. Could you confirm if you have a different configuration (in my example, I've used my user, but that could also be a user group)?

Also, you mentioned configuring this at the project level, but it may be the case that there are some other rules at the repository level (Repository Level > Branch Restrictions) that could be playing a role in this. So I would recommend checking if there is any other more strict branch restriction at the repo level on that particular repository you identified developers were not able to commit.

It's important to note as well that in addition to being allowed in the branch restrictions, the user group must also have at least write access to the project/repository in question to make new commits. In this case, could you please confirm if the user group you're using for the test has write access granted in the project (Project Settings > Project permissions) to which the testing repository belongs?

If you have any questions, feel free to ask.

Thank you, @Rodrigo Olivares B2 !

Patrik S