Promote Source/Target Branch Fields in Merge Request Form

Problem to solve

Prevent data I entered in merge-request description (and other fields) from being lost + properly express important fields in UX.

Intended users

All users

Further details

Use-case: I create an MR, start by entering title+description, but after scrolling down realize that I haven't properly set the source/target branches. When I change branches I'll lose data I've just entered, so I must go through extra steps to retain it. It would be nice to just remember to scroll down first before I enter everything, but the UI should help me.

Proposal

Move the source/target branches fields near the top of the Merge Request form. They are arguably the most important fields on the form, more important than the "description" field, so I propose moving the fields to the #1 (closed) position or just below "Title".

Permissions and Security

n/a

Documentation

Documentation which contains screenshots of the MR form or step-by-step instructions may need to be updated.

Testing

Testing is limited to regression testing if only the field position is changed.

What does success look like, and how can we measure that?

No regressions

What is the type of buyer?

This should be deployed to EE and CE imo

Links / references