Hi team,

We've had a customer provide feedback about the current state of the merge queues feature as follows:

• We had deployment to Test_canary environment restricted to only branch test8.1.
  But since adopting merge queues, Bitbucket runs merge queue builds on temporary branches named bitbucket-merge-queue-. *
• To make those builds work, we had to whitelist that pattern for deployments too - which defeats the purpose of having branch-based deployment restrictions in the first place.

This limitation is known (see below), but should be addressed to make the feature more useful for our customers:

• Bitbucket creates temporary branches matching the pattern bitbucket-merge-queue-* to run merge queue builds. Make sure there are no branch restrictions that block this pattern (for example, permissions that prevent commits from being created on branches matching bitbucket-merge-queue-*).