Merge Request enhancement ~ Store a preference for the default target branch of all merge requests within a project.
### Problem to solve
Low hanging fruit ~ Merge Request enhancement:
Let Gitlab users specify the default target brach a per-account/per-project setting. For merge requests, being able to configure this in advance saves clicks and is objectively a better 'UX'.
One given option for the default target branch should be the first parent/base branch of the current branch.
### Intended users
All roles.
* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)
### Further details
N/A
### Proposal
N/A
### Permissions and Security
N/A
### Documentation
N/A
### Testing
N/A
### What does success look like, and how can we measure that?
Measure the time it takes to open a merge request and see that it has reduced.
### What is the type of buyer?
Freetier
### Links / references
N/A
issue