Problem Statement:
When I have a forked repository in a Bitbucket project and create a new PR, the default destination is master/main of that fork. For example, the following repo in source and destination is a fork of an original repo, but creating a PR defaults the destination value to the fork and master branch:

In my experience, this makes it easy for a developer to accidentally merge into the fork's master branch and desync it. Then my team has to go through the process of correcting this.
Generally, our common use case is to merge into master/main of the origin branch instead.

Enhancement:
In the settings, I would like to be able to specify what the default Destination repository for PRs should be:

Then when PRs are opened on this fork repo, the dropdown value will default to this repo specified in the settings.