UX Scorecard Recommendations: Create FY25-Q3 Source Code - Branch Rules
This is a collection of recommendations from the UX Scorecard - Create FY25-Q3 OKR - Source Code for branch rules.
Issues
|
# |
Category | Description | Recommendation | Issue |
|---|---|---|---|---|
| 1 | Performance | Branch rule creation was laggy | Address performance issues with branch rule creation | |
| 2 | Performance | Abnormal bug caused page loads/save actions to completely stall, causing new GitLab issues | Fix latency issues | |
| 3 | Confusing mental models |
User did not equate “Create protected branch” to “Creating a new branch rule” and as a result could not find the start of how to create a branch rule with a wildcard. User ended up using Duo to help execute the task. |
Revisit mental model or wording for "Create protected branch" button | |
| 4 | Confusing mental models | Setting “No one” as “Allowed to merge” still shows up as “1 user” in the overview table | Remove "Allowed to merge: 1 role" if "No one" is selected | |
| 5 | Confusing mental models |
Branch rules for “All branches” and for “*” wildcard are shown as 2 separate branch rules even though they are targeting the same branches |
Combine branch rule if user already has "All branches" / "*" branch rule created. Provide adequate error handling or redirection if needed. |
|
| 6 | Confusing mental models | An approval rule with 0 “Approvals required” can exist, even if it is not enforcing anything | Discuss whether to allow approval rules with 0 "Approvals required" | |
| 7 | Confusing language | User was not sure what the distinction between “Project groups” vs “All groups” was in the “Add approval rule” drawer | Provide in-context information to help users understand vague UI elements |
Opportunities
|
# |
Category | Recommendation | Issue |
|---|---|---|---|
| 1 | Efficiency | More information on the Branch Rules overview page so users don’t have to click into the details for every branch rule | |
| 2 | Efficiency | Keyboard shortcuts like hitting "Enter" when creating a new branch rule in the "Create branch rule" modal | |
| 3 | Flexibility | Expand wildcard capabilities to allow full regex, multiple wildcards, or wildcard exclusions | |
| 4 | Flexibility | Increased granularity of settings to accommodate complex requirements | |
| 5 | Flexibility | Define branch rules in a code file, which is a standard in development | |
| 6 | Context | Enter a username to see which branch rules apply to that user | |
| 7 | Context | For any branch, surface the branch rules that apply to that branch and allow any user to see it | |
| 8 | Context | Give more information / contextual help to help with volumes of Groups | |
| 9 | Context | Link to the documentation | |
| 10 | Context | Surface global policies. One user noted that global policies he knew were in place sometimes did not show up in Branch rules. | |
| 11 | Scale | Applying rules across hundreds of branches | |
| 12 | Scale | Ability to copy settings | |
| 13 | Scale | Bulk actions / quick actions |
Assets
- Planning document: UX Scorecard: Source Code (Branch Rules) - Create FY25-Q3 OKR
- FigJam canvas: UX Scorecard Journey Map: Source Code - Branch Rules
- Walkthrough slides: Figma | PDF
- Walkthrough video: UX Scorecard: Source Code - Branch Rules (October 2024)
- Calculations: UX Scorecard Calculations: Source Code (Branch Rules)
- DoveTail project: UX Scorecard - Source Code workflow FY25Q3
Edited by Alyssa Trinh