Hi team,

Currently, branch permissions functionality only allows for configuring permissions against target branches. We have had a user request that this be configurable for source branches as well - their use case is as follows:

We have multiple development teams working on the same repositories, with each team using a dedicated Jira project and having different merge check requirements.

Branch names are based on Jira ticket keys, which allows us to identify the team from the branch name—for example, BTK-111, BSTBL-222, etc. This naming convention is important due to our Jira–Bitbucket integration.

Use case scenarios:

Case: Team BTK (Jira Project: BTK)

• When a pull request is created from a BTK branch (e.g. BTK-111 → feature/BTK-987) to any branch:
  • All BTK team members are added as reviewers
  • Require 2 approvals to merge
• When a pull request is created from a BTK branch to master (e.g. feature/BTK-987 → master):
  • BTK team members and QA team members are added as reviewers
  • Require 1 approval from each group (e.g. developer group, QA if applicable)

Case: Team BSTBL (Jira Project: BSTBL)

• When a pull request is created from a BSBTL branch to master (e.g. feature/BSTBL-222 → master):
  • BSTBL team, BTK team, and QA team are added as reviewers
  • Require 1 approval from each group

Since the branch naming clearly maps to the Jira project and the responsible team, being able to configure default reviewers and merge checks based on the source branch pattern would allow us to automatically enforce team-specific review policies, reduce manual reviewer assignment, and prevent incorrect or insufficient approvals.

Cheers!

• Ben (Bitbucket Cloud Support)