Mark merge request as "draft" with a single click
Make draft merge request feature discoverable
Problem
Marking an MR as draft/wip is great to signal to others that the work in on-going and not ready for review, however, the feature has low discoverability and using is not intuitive unless you go into edit mode and read all the text on the page.
Proposal
Update the multi-action dropdown button to offer the ability to "mark as draft" (dropdown would offer 3 total options, along with "close" and "report abuse")
| Expanded | On form |
|---|---|
 |
 |
- state when MR is NOT in DRAFT mode:
Mark as draft
Close merge request
Report abuse- state of button when MR is in DRAFT mode
Mark as ready
Close merge request
Report abuseOriginal proposal
| Option 1 | Option 2 |
|---|---|
| Update the multi-action dropdown button to offer the ability to "mark as draft" (dropdown would offer 3 total options, along with "close" and "report abuse") | Offer a new button in the MR screen |
|
 |
Release Notes
Creating a merge request is a great way to share your contribution with others and get the conversation started. Even if the code is not ready to be merged. In order to signal to others that a contribution is not ready to be reviewed/merged, we can prefix the merge request title with draft (formerly known as wip). This is useful, however, it entails going into edit mode, navigating to the merge request title, and typing the required prefix.
To make it easier to use this feature, we have introduced the Mark as draft button to merge requests. With a single click, you can indicate your work is in progress and not ready to be merged/reviewed.
UX Research
In the Category Maturity Testing for Code Review, the WIP feature for Merge Requests is not easily discoverable. The most common ways participants signaled the in-progress status of the MR was by 1) closing the MR or 2) applying a label. Dovetail insight