## Proposal We have notoriously long button labels for the MWPS and MTWPS strategies: `Merge when pipeline succeeds`, `Start|Add to merge train when pipeline succeeds`. The [NN Group suggests 4 values of better link labels](https://www.nngroup.com/articles/better-link-labels/), that can also be used for button labels: > Write **specific** links that set **sincere** expectations and fulfill them, that are **substantial** enough to stand alone while remaining as **succinct** as possible. These 4 values must be balanced. In the case of our MWPS and MTWPS buttons, I believe these values are out of balance: the button labels are overly **specific**, **sincere** and **substantial**, sacrificing **succinctness**. ## Solution validation [Findings](https://gitlab.com/gitlab-org/ux-research/-/issues/1568#-findings "Solution validation Research: Auto-merge") From a solution validation exercise we learnt that users are comfortable not getting very specific details about the strategies, as long as they have clarity on the next steps in the merge process and a method to expand the strategy if required. ### Competition In the [competitive analysis of code review merge checks UX](https://gitlab.com/gitlab-org/gitlab/-/issues/300767 "Competitive analysis of code review merge checks UX"), we discovered that Azure DevOps, Bitbucket, and GitHub all use the “auto-merge” or “automatic merge” terminology. ## :dart: Plan | Sequence | Issue | Purpose | Comments | |----------|-------|---------|----------| | 1 | Design:Simplify MWPS/MT/MTWPS with just auto-merge on merge widget | Work on a design proposal for how the `Auto merge` option would appear to users on the MR page | | | 2 | Solution validation research | use the design proposal from :one: to perform a validation exercise and understand the dependencies | [Findings](https://gitlab.com/gitlab-org/ux-research/-/issues/1568#-findings "Solution validation Research: Auto-merge") | | 3 | [Design: Replace merge strategy labels with Auto-merge](https://gitlab.com/gitlab-org/gitlab/-/issues/359057) | Make changes to the copy of the existing auto-merge design to bring out more clarity on the next steps in the merging process. Follow the progress of https://gitlab.com/groups/gitlab-org/-/epics/5589 | https://gitlab.com/gitlab-org/gitlab/-/issues/359057 | | 4 | [Replace merge strategy labels with `Auto-merge`](https://gitlab.com/gitlab-org/gitlab/-/issues/359059 "Replace merge strategy labels with `Auto-merge`") | ~~Start rolling out the change by replacing the `Merge when pipeline succeeds`, `Start/Add to merge train when pipeline succeeds` with `Auto-merge`~~ | The solution in https://gitlab.com/gitlab-org/gitlab/-/issues/359057 already replaces the merge strategy labels. there's no need for a new proposal for this issue.| | 5 | Improve merge train settings to match new merge strategy options | Re-group the merge train options to match the new layout for merge strategy | https://gitlab.com/gitlab-org/gitlab/-/issues/340393 |