UI for Pull Requests chooses branches backwards

Issue Summary

The UI default source branch → destination branch workflow is choosing branches backward.

Steps to Reproduce

1. Set master/main branch as Development branch
2. Set a branch "prod" as Production branch in the Branching model https://bitbucket.org/<workspace>/<repository>/admin/branching-model
3. Add commits until one is ahead of other
4. Open a Pull request

Expected Results

When a feature branch exists, the source should be the feature branch, destination branch should be the development branch.

When no feature branch exists, and the development branch is ahead of the production branch, the source should be the development branch (master), destination branch should be the production branch.

Actual Results

The current bug has its backward.

Workaround

• Currently, there is no known workaround for this behavior. A workaround will be added here when available