KR: Prioritize the existing UX recommendations for Merge Requests

• Refine the existing recommendations as needed, add a severity label, and provide to Development by May 13, 2020: #7620 (closed)
  • Recommendations should address user problems that already exist with the current functionality, not add new features or solve user problems that are not covered by the product today.
  • Recommendations from past UX Scorecards and other existing issues that could be UX bugs.
  • Other heuristics for recommendations/problem selection (before prioritization):
    • Popularity and Number of months/years the issue has been open
    • CEO interest
    • Tier (Free, Bronze, Silver or Gold)
    • Small change with big impact
      • How many categories/customers/users does this issue affect? (importance)
      • Would this be a minimal viable change? (feasibility)
        • Accomplishable in one milestone (month)
        • The problem is understood (low uncertainty)
        • A solution has been proposed that is well-understood (yet may need more refinement)
        • Minimal backend work
  • Add them as related to this issue.
  • Set up prioritization session with @danielgruesso, @m_gill and @andr3
  • Post screenshot of Mural board and top 5 issues in order of prioritization
• Run an internal research session with Sid to capture his feedback as one input to MR refinement by May 31, 2020: notes and recording

Results

Prioritization session

Mural board

Scheduled Issues

Stage Group	Name	Relevant labels	Milestone	Merge Request
groupsource code	Explicitly show outdated status of suggestions that cannot be applied	Impact 3 / Feasibility 4 ~S3 CEO Interest	Closed in %13.1	gitlab-org/gitlab!33357 (merged)
groupsource code	Number of required approvals is counterintuitive on the merge request list	Impact 3 / Feasibility 2 — ~S3	Closed in %13.1	gitlab-org/gitlab!33329 (merged)
groupsource code	Accept multiple merge request suggestions at once	direction	Closed in %13.1	gitlab-org/gitlab!22439 (merged)
Community contribution	Improvement in UI for diffing two versions		Closed in %13.1	gitlab-org/gitlab!31770 (merged)
Community contribution	Comment drafts in Merge Request Reviews (Batch Comments) are showing a lonely dot		Closed in %13.1	gitlab-org/gitlab!31783 (merged)