Skip to content
GitLab
Next
    • Why GitLab
    • Pricing
    • Contact Sales
    • Explore
  • Why GitLab
  • Pricing
  • Contact Sales
  • Explore
  • Sign in
  • Get free trial
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #227217

Merge Request Reviewer workload dashboard (discovery)

Problem to solve

It is hard to keep track of certain kind of activity, in this particular feature proposal, how many Merge Requests an individual reviews.

This is interesting for the Developer, as they for example could see if they are at capacity with reviews. It is also interesting for Developers to find another developer that is not "at the limit" when it comes to reviews.

For Development Team leads it can be interesting to see how much time is spent on reviews in order to account for it in a planning phase.

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)

User experience goal

JTBD: When I have an MR that needs reviewing, I would like to understand which maintainers are available for review, so that I can assign them to review my MR confidently.

Proposal

I have built this prototype for a dashboard: https://leipert-projects.gitlab.io/maintainer-workload/

Screen_Shot_2020-07-07_at_18.24.32

This dashboard functions on the group level (gitlab-org) in this example and combines the following information:

  1. Availability: Whether a person is available or not. If they aren't available, they can be hidden from the view. Currently GitLab does support setting a status, but we do not know whether a person is available or not. This could be beneficial in other views in GitLab as well and might not be needed for an MVC.
  2. Category: Each Person has one or more "categories", e.g. Backend Maintainer / Frontend Maintainer. We don't have the possibility to set this currently in the product, only could fall back on a persons role (e.g. Maintainer, which wouldn't differentiate between Frontend / Backend for example)
  3. Currently assigned Review MRs: All MRs in that group that are assigned which are not authored by the user.
  4. Review assignment events: All assignment events of Review MRs. I am currently parsing system notes and do not know whether the data is available in products.

Further details

Permissions and Security

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited Oct 20, 2020 by Tim Poffenbarger
Assignee
Assign to
Time tracking