Merge Request Widgets: Research Synthesis and JTBD Outline
What’s this issue all about?
Assessing our prior research to consolidate existing recommendations for usability improvements to the MR widget.
Understanding JTBD and internal stakeholders associated with each widget component.
Guiding research questions
- Which stage groups are contributing to the MR widget (stakeholders)?
- Accessibility - Verify:Testing
- Approvers - Create:Code Review, Secure:Threat Insights (Vulnerability Management)
- Branches - Create:Code Review
- Browser performance test - Verify:Testing
- Code Quality - Verify:Testing
- License Compliance - Secure:Composition Analysis
- Merge - Create:Code Review
- Merge Trains - Verify:Continuous Integration
- Metrics - Verify:Testing (Load Testing)
- Pipelines - Verify:Continuous Integration
- Merged Result Pipeline - Verify:Continuous Integration
- Security - Secure:Static Analysis (SAST, Secret Detection), Secure:Dynamic Analysis (DAST), Secure:Fuzz Testing, Secure:Threat Insights (Vulnerability Management)
- Terraform - Configure
- Test Summary - Verify:Testing
- Who are the primary intended consumers of information presented in the MR widget?
- Software Engineers: Accessibility, Approvers, Metrics, Test Summary, Merged Pipeline Results, Security
- DevOps Engineers: Metrics, Merged Pipeline Results, Terraform
- Security Analysts: License Compliance, Security (SAST,DAST), Security Approval
- Other
- System Administrators: Metrics
- Quality Engineers: Accessibility
- What are the main jobs users need to accomplish on the MR page?
- Understand the impact of changes introduced into an MR
- Resolve issues that block an MR from being merged
- What is the purpose of each element in the MR widget? - When and why was it added?
- How do users utilize the MR widget?
- What works well or doesn't well?
Slide deck with research summary: https://docs.google.com/presentation/d/18BAZhPyNfbA81YhdCCR6BbvNMA0R224cF5nq8CUSB9k/edit?usp=sharing
Sources
-
Merge Request pipelines &2056 (closed), https://gitlab.com/gitlab-org/ux-research/-/issues/386, https://gitlab.com/gitlab-org/ux-research/-/issues/244 -
Merge Request page https://gitlab.com/gitlab-org/uxr_insights/-/issues/356, https://gitlab.com/gitlab-org/uxr_insights/-/issues/368, &1274 (closed) -
Security approvals &2347 (closed) -
MR approval rules usability testing &2333 (closed) -
SAST setup &1784 (closed) -
Accessibility https://gitlab.com/gitlab-org/uxr_insights/-/issues/962, &2639 -
Run merge request pipeline positioning #266 (closed), &2252 (closed) -
License Management https://gitlab.com/gitlab-org/uxr_insights/-/issues/248, &1225 (closed) -
File-by-file https://gitlab.com/gitlab-org/uxr_insights/-/issues/650, https://gitlab.com/gitlab-org/uxr_insights/-/issues/654, https://gitlab.com/gitlab-org/uxr_insights/-/issues/655, &2070 (closed)
Links
- Feedback doc (WIP): https://docs.google.com/document/d/1JesI9WIjkndKxFExT3BAEDgrv3ieL4G3eUfD5bYJDw4/edit?usp=sharing
- Related usability issues: #1073 (closed)
- Figma map: https://www.figma.com/file/jEUIZa5W0JvsR6lwgxwOYn/MR-Widget?node-id=0%3A1
- Async design critique insight: https://dovetailapp.com/projects/14109fbc-dfdd-4204-a54e-9c80ba8b7bba/insights/present/01f97e1e-288e-471e-ab7f-1927ce0449a8
- Async design critique feedback - Link
- Related docs/issues/epics: https://docs.gitlab.com/ee/user/project/merge_requests/, gitlab#7669, &3869, https://docs.gitlab.com/ee/api/merge_requests.html, https://docs.gitlab.com/ee/user/project/merge_requests/reviewing_and_managing_merge_requests.html#pipeline-status-in-merge-requests-widgets
Edited by Pedro Moreira da Silva