Skip to content

Use workload capacity when returning reviewers to find reviewers with fewer reviews currently

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem

Finding a relevant reviewer for my merge request is a great first step, however, if my change is time sensitive or if the selected reviewer is overloaded with work, I have no way of knowing my requested review will possible be delayed.

Proposal

We should use the number of MRs that a user is currently assigned for review as a factor in how highly they should be returned in the sorted list for reviewers. This number is potentially challenging to calculate as an absolute number that makes sense for all users in all cases, so we should potentially look at more relative sorting. For example:

  • User A, B, and C are all acceptable reviewers for a particular MR
  • User A has 2 MRs for review already
  • User B has 4 MRs for review already
  • User C has 0 MRs for review already

When the list of users is returned (barring any other criteria) we'd expect to see:

  1. User C
  2. User A
  3. User B

This would give us relative positioning compared to others who could review with an assumption that fewer assigned reviews means more capacity to take on additional reviews.

Original Proposal

Display capacity next to user on the reviewers' drop-down. We'll need to decide how to calculate capacity as there are a couple of options.

image

Edited by 🤖 GitLab Bot 🤖