Dataset: Issues & Pull Requests
Entity: Pull Requests
Field ID: requested_reviewer_usernames
Type: List of text values
Description: The list of people usernames assigned as reviewers on the pull request. Note that usernames are app specific.
Source: App
Transformation logic: N/A
From: |
|
Github (PRs, Issues) |
|
Gitlab (PRs, Issues) | Assigned reviewers who have NOT left a review yet |
Bitbucket (PRs) | Assigned reviewers who have NOT left a review yet |
Azure DevOps (PRs, Issues) | Assigned reviewers who have NOT left a review yet |
JIRA (Issues) | N/A |
ClickUp (Issues) | N/A |
Trello (Issues) | N/A |
Reporting Use Cases
The Requested Reviewers field is essential for managing your team's code review process in real-time. As a list of strings, it allows you to track current review assignments, create personalized work queues, and analyze the distribution of review workload across your team.
Filtering for Actionable Review Queues: This is the most common and powerful use of this field. You can build widgets that show exactly who needs to review what.
Personal "To Review" List: The includes me operator is perfect for creating a dynamic list of pull requests waiting for your review. A filter where
Requested Reviewers includes mewill automatically show each user their pending reviews.Team Workload: Use the
contains any ofoperator to see all PRs assigned to a specific group of reviewers.Find Unassigned Reviews: Identify pull requests that are stalled because they haven't been assigned to a reviewer yet by using a filter where
Requested Reviewers length = 0.
Reporting on Review Workload: To accurately measure the current review load on each team member, you must use the
FLATTENfunction to treat each reviewer as a separate entity.Pending Reviews per Person: You can create a bar chart showing the number of open pull requests each person is currently assigned to review. To do this, use a custom dimension with the formula
FLATTEN(requested_reviewer_usernames)and aCOUNT()metric. This provides a clear, at-a-glance view of your team's active review workload.
Analyzing Review Process Health: You can use custom formulas to measure the efficiency and collaboration patterns of your review assignments.
Reviewer Count per PR: A metric like
AVG(LENGTH(requested_reviewer_usernames))will tell you the average number of reviewers assigned to each pull request. A low number might indicate a need for more cross-functional review, while a very high number could suggest process inefficiency.