UI copy update MR empty state to help platform switchers understand GitLab terminology
Problem to solve
Growth is working on improving new-user onboarding.
UX research shows that GitLab-specific terminology increases the learning curve for new users from other platforms.
Confusion about the term Merge requests came up in multiple sessions. (UXR slide). Project was also a confusing term.
Proposal to discuss
- Re-word the first-time empty state to help first-time users understand what a MR is (
https://.gitlab.com/group/project/-/merge_requests)- The first-time empty state is shown when there have never been MRs. This issue does not touch the "No open MRs" empty state (screenshot)
- Remove the Email a MR from the empty state to keep the empty state focused on the primary use case (no events fired in the last 30 days)
| Current empty state | Proposed empty state |
|---|---|
![]() |
![]() |
Edited by 🤖 GitLab Bot 🤖

