Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: review_last_requested_at
Type: Datetime
Description: The datetime at which a pull request review was last requested. For issues, it is the timestamp of the newest request across all resolving pull requests.
Source: Calculated
Transformation logic:
Pull requests: It is the datetime of the last
review requestedevent, which happens when a reviewer is assigned.Issues: it is the datetime of the newest request for review across all resolving pull requests. Resolving pull requests are pull requests that reference the issue via auto-closing keywords.
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs, Issues) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The Review Last Requested At field is a crucial timestamp that marks the most recent time a review was requested for a pull request. It is especially important for workflows where PRs undergo multiple review cycles, as it signals the start of the final or most current round of feedback, making it essential for measuring the efficiency of your rework and final approval phases.
Measuring Final Review Cycle Time: This field serves as the starting point for the final review cycle.
You can calculate the time from the last review request to final approval with the custom formula
(review_approved_at - review_last_requested_at) / DAY(). This metric helps you understand how quickly your team can turn around a pull request once all rework is complete and it's submitted for its final review.
Analyzing Rework and Re-review Loops: By comparing this timestamp with the first review request, you can identify PRs that have gone through multiple rounds of feedback.
A custom formula dimension like
(review_last_requested_at - review_requested_at) / DAY()calculates the total duration of the "rework and re-request" phase. A high value indicates that a PR went through a lengthy cycle of changes and feedback.
Filtering for Stalled Final Reviews: You can create reports to find pull requests that are waiting for a final review but have been sitting idle.
A filter where
Review Last Requested At before 3 days ago and Review State = "PENDING"will create a list of all pull requests that are blocked waiting for a final sign-off, helping you identify and resolve bottlenecks in the last stage of your review process.