Merge request approval rules
What’s this issue all about?
In a first quick usability test around our merge request page, the approval rules stood out as the one aspect where users had the most trouble understanding our UI gitlab-design#441 (closed).
What questions are you trying to answer?
Given the amount of complexity behind this topic and the amount of work that already went into this feature, and the fact that we did not test it with users at all so far, it would be a good first step to do a short usability study to see which parts of the current UI our users struggle the most with https://gitlab.com/gitlab-org/gitlab-ee/issues/1979.
What assumptions do you have?
There are multiple assumptions we have after our first test:
- It's unclear to newer users what the difference between assignee and approver is
- Users have trouble understanding the concept of multiple approval groups that each have their separate rules
- Users have trouble understanding the default approval group and how to replace it/add new ones
- Users have trouble understanding what the name for the approval group is for
What decisions will you make based on the research findings?
Depending on the severity of the problems our users are facing, we might have to look into how to restructure the UI around this feature.
What's the latest milestone that the research will still be useful to you?
Methodology
Usability testing with 5 GitLab users who are using the MR Approvers feature (Starter/Premium/Ultimate or Bronze/Silver/Gold). Users should access their own instance or a test instance. After the usability testing portion, we will present a few mockups to the users for feedback.
- Tasks: setting up approvals, editing approvals, adding or removing an approval, replace default approval group, recognize names of approval groups, create a
Vulnerability-Check
rule, create aLicense-Check
rule. - If time permits, get feedback on mockups: https://gitlab.com/gitlab-org/gitlab-ee/issues/12185#note_182213354
Progress
-
Draft script for usability testing [Deadline: Weds Nov 20th] -
Finalize script [Deadline: Thurs Nov 21st]
-
-
Send screener survey to segment of GitLab First Look [Deadline: Thurs Nov 21st] -
Schedule 5 users [Deadline: Tues Nov 26th] -
User 1, Tuesday, November 26, 2019 at 11am PT -
User 2, Wednesday, November 27, 2019 at 10:30am PT -
User 3, Monday, December 2, 2019 at 1pm PT -
User 4, Wednesday, December 4 at 10:30am PT -
User 5, Wednesday, December 4 at 11:15am PT
-
-
Conduct usability testing sessions [Deadline: Fri Dec 6th] -
Purchase Amazon gift cards [Deadline: Fri Dec 6th] -
Edit and analyze videos [Deadline: Tues Dec 17th] -
Document insights as issues in the Insights Repository [Deadline: Weds Dec 18th] -
Schedule call to discuss findings [Deadline: Weds Dec 18th]
- Testing script: https://docs.google.com/document/d/1IsLExUt908bfKiPCQICQkg4erYsuFgodRfxq0dV8lE8/edit?usp=sharing
- Note-taking sheet: https://docs.google.com/spreadsheets/d/1VNkCkZZUlmHbQeAnltxA_WvYW0D7t-BulfkWgMWvRIk/edit?usp=sharing
- Insights Epic: &2333 (closed)
- Video folder: https://drive.google.com/open?id=1cZ1dLYP3mdd0pY8e7N6FyamYj9JIJ6QY
- Participants: https://docs.google.com/spreadsheets/d/1w_L13H7_xcXOVUV3pNIqpnliXMierrNRRoaomuRSlFo/edit?usp=sharing