Branch Permission overlap and groups

[JRob]

The Branch permissions page (here) is unclear about this scenario:

I have two groups (one is a subset of the other). I'd like to restrict rewriting branch history in general (our practice is to simply create a new branch for the rewrite due to interop with other tools that go haywire on a branch rewrite) so I've created a wildcard (*) branch permission which Group A has write access to and the "Rewriting branch history is not allowed" is checked.

However, I don't want everyone to have write to master so I created a second group Group B that has write access to master.

Will Group A have write access to master?  The branch permissions page does not address this particular scenario but it does seem to say that if two individuals (Alana and Harvey) are in this scenario than the rules would combine. I don't want Group A and Group B to combine write access to master, I want to restrict Group A's access to master. Can this be done?

In summary the rule set I'm looking for is:

1. If user is in Group A then they cannot rewrite branch history on any branch (*).
2. If user is in Group A then they do NOT have write access to master
3. ONLY if user is in Group B then they can write to master.

I would be okay with Group A being the special group of Everybody if that changes things. It would also be great if someone from Atlassian could update the Branch permissions page to include some groups in the Branch permissions overlap section.

[Razvan Negrea]

Please, I have the same question. I just can't figure out a way to:

• Allow myself full permissions on any (*) branch, inc. rewriting history and deleting any branch.
• Set other users to write, but not rewrite history or delete master.

It seems that every time I try to do this, I either allow everyone to rewrite or I can't force push "master" myself.