Hello,
If you create a branch from a release branch, let's say release/1.1, you would expect that Bitbucket by default proposes to merge into this release branch.
Unfortunately, this is not the case, it can propose to merge into master instead for instance.
It is unexpected and a bit error prone.
Thanks to automatic branch merging (which is activated in our case), it should detect the corresponding ancestor.
Is there a solution for this ?
Thanks in advance,
Chris
