Currently, when we create a branch restriction with the pattern, say, release/{}{}, and another branch restriction with release/123, the restrictions configured at the release/123 do not adhere and it is overridden by the branch restriction of release/.

The warning displays below message:

Includes restrictions set in branch pattern: release/* (Release)

The suggestion is to provide branch restriction independently even if there is a match glob pattern.