Improve text of MR empty state
This is an actionable insight from the UX Department: MRs experience async critique research (insight).
What
The text of a merge request's empty state could be improved on the following points:
- "Interested parties" is a really stuffy, formal term. It also seems a little out-of-place and vague since the rest of the message is directed to "you." Interested parties sounds like it could range from my team members to random GitLab users.
- It talks a lot about commits, but maybe I don't know what a commit is or how it relates to creating a file.
- At the end of the message, the calls-to-action don't have buttons. It says “push new commits or use a different branch” but the only button is “Create file”.
- To be addressed in #291999 (closed)
Designs
- Show closed items
- Issue#324228BacklogCategory:SAST GitLab Core GitLab Premium GitLab Ultimate [deprecated] Accepting merge requests backend devops application security testing group static analysis section sec type feature
- Epicgitlab-org#130501219Feb 10 – Sep 13, 2024Category:SAST devops application security testing feature consolidation group static analysis section sec type feature
- Issue#439046BacklogCategory:SAST backend customer devops application security testing group static analysis section sec
- Issue#425084BacklogCategory:SAST devops application security testing group static analysis section sec type feature workflow planning breakdown
- Issue#373117515.9Category:SAST Deliverable Track Health Status [DEPRECATED] devops application security testing feature enhancement group static analysis section sec type feature workflow complete
- Issue#36295816.0Category:SAST Deliverable GitLab Free GitLab Premium GitLab Ultimate backend customer devops application security testing documentation group static analysis missed-deliverable missed:15.7 missed:15.8 section sec type feature workflow complete
- Issue#36284915.10Category:SAST Deliverable [deprecated] Accepting merge requests devops application security testing feature consolidation group static analysis section sec type feature workflow complete
- Issue#35266615.4Category:SAST GitLab Free GitLab Premium GitLab Ultimate backend devops application security testing documentation group static analysis missed:15.2 missed:15.3 section sec type feature
- Issue#34725815.4Category:SAST backend customer devops application security testing feature enhancement group static analysis section sec type feature workflow production
- Issue#335221BacklogCategory:SAST [deprecated] Accepting merge requests devops application security testing group static analysis maintenance workflow section sec type maintenance
- Issue#33406514.02Category:SAST backend devops application security testing group static analysis section sec type maintenance workflow in dev
- Epicgitlab-org#544064Feb 18 – Apr 17, 2021Category:SAST devops application security testing group static analysis section sec type feature
- EpicClosedgitlab-org#56881013Jan 18 – Jun 17, 2021Category:SAST backend devops application security testing group static analysis section sec
- Issue#331801BacklogCategory:SAST [deprecated] Accepting merge requests backend devops application security testing feature enhancement group static analysis section sec type feature
- Issue#330578BacklogCategory:SAST Product Feedback SAST: New Scanner [deprecated] Accepting merge requests customer devops application security testing group static analysis section sec
- Epicgitlab-org#57971015Apr 18 – May 17, 2021Category:SAST [deprecated] Accepting merge requests backend devops application security testing feature enhancement group static analysis section sec type feature
- Issue#327236BacklogCategory:SAST [deprecated] Accepting merge requests backend devops application security testing feature enhancement group static analysis section sec type feature
- Issue#321204BacklogCategory:SAST [deprecated] Accepting merge requests backend devops application security testing group static analysis section sec type feature
- Issue#118496BacklogCategory:SAST SAST: Integrate customer devops application security testing group static analysis section sec type feature workflow start
- Issue#26206813.11Category:SAST Deliverable Discovery SAST: Integrate [deprecated] Accepting merge requests backend devops application security testing group static analysis missed-deliverable missed:13.10 missed:13.9 section sec type feature workflow planning breakdown
- IssueClosed#300486BacklogCategory:SAST [deprecated] Accepting merge requests auto updated backend devops application security testing group static analysis section sec type feature
Blocks
Relates to
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
added Category:Code Review Workflow Technical Writing UI text devopscreate groupcode review merge requests sectiondev + 1 deleted label
- Pedro Moreira da Silva changed title from Improve text of merge request empty state to Improve text of MR empty state
changed title from Improve text of merge request empty state to Improve text of MR empty state
- Pedro Moreira da Silva changed the description
Compare with previous version changed the description
- Pedro Moreira da Silva marked this issue as related to #291999 (closed)
marked this issue as related to #291999 (closed)
- Pedro Moreira da Silva marked this issue as related to ux-research#1073 (closed)
marked this issue as related to ux-research#1073 (closed)
- Pedro Moreira da Silva added featureenhancement label
added featureenhancement label
- 🤖 GitLab Bot 🤖 added typefeature label
added typefeature label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1274 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1274 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1367 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1367 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1435 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1435 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1512 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1512 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1598 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1598 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1686 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1686 (closed)
- Pedro Moreira da Silva mentioned in issue create-stage#12791 (closed)
mentioned in issue create-stage#12791 (closed)
- Amy Qualls assigned to @aqualls
assigned to @aqualls
- Maintainer
I see matches in
app/views/shared/empty_states/_merge_requests.html.haml
app/assets/javascripts/vue_merge_request_widget/components/states/nothing_to_merge.vue
Current wording:
Merge requests are a place to propose changes you've made to a project and discuss those changes with others.
Interested parties can even contribute by pushing commits if they want to.
Currently there are no changes in this merge request's source branch. Please push new commits or use a different branch.
- Maintainer
When I create the MR, the pipeline will be long each time. Easier to hammer out the phrasing here.
I think we're burying the lead here, and talking about what we want the user to know first, rather than what the user cares about. What if we start with a description of the current state, then talk about how to get work done?
This merge request contains no changes.
Use merge requests to propose changes to your project, and discuss those changes with your team. To make changes to files, push a new commit, or update the merge request to use a different branch.
@phikai Sending over your way for thoughts. This is emphatically a first draft. On top of phrasing changes from you, we'd need to figure out what pages to link and what words to link them with.
1 Collapse replies - Developer
I think we're burying the lead here, and talking about what we want the user to know first, rather than what the user cares about. What if we start with a description of the current state, then talk about how to get work done?
THIS MAKES A TON OF SENSE!!! Thank you so much for thinking in this way.
This merge request contains no changes.
Use merge requests to propose changes to your project, and discuss those changes with your team. Make changes to files[] or push a new commit to get started.
I think this simplifies it enough. WDYT @aqualls?
- Maintainer
@phikai Like it. I've spun up the beginnings of a MR. I'll need FE help; because of the links, it goes past a simple text replacement.
- Developer
@aqualls Can we close this?
- Amy Qualls assigned to @phikai and unassigned @aqualls
- Kai Armstrong assigned to @aqualls and unassigned @phikai
- Amy Qualls mentioned in merge request !53917 (merged)
mentioned in merge request !53917 (merged)
- Amy Qualls changed milestone to %Next 1-3 releases
changed milestone to %Next 1-3 releases
- Pedro Moreira da Silva mentioned in issue create-stage#12806 (closed)
mentioned in issue create-stage#12806 (closed)
- Amy Qualls changed milestone to %13.11
changed milestone to %13.11
- Amy Qualls changed milestone to %13.10
changed milestone to %13.10
- Amy Qualls closed
closed
- Amy Qualls added twfinished label
added twfinished label
- Pedro Moreira da Silva mentioned in merge request gitlab-com/www-gitlab-com!76870 (merged)
mentioned in merge request gitlab-com/www-gitlab-com!76870 (merged)
- Lauren Evans removed 1 deleted label
removed 1 deleted label
- Lauren Evans added Actionable InsightProduct change label
added Actionable InsightProduct change label
- Adam Smolinski added closedcomplete label
added closedcomplete label