Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: first_comment_after_review_requested_at
Type: Datetime
Description: The datetime of the first comment made after a peer review was requested. This timestamp may help identify when a peer review started for GitLab and Bitbucket, which do not support a formal review system. For GitHub, use the field first_review_created_at instead.
Source: Calculated
Transformation logic:
Pull requests: Datetime of the first comment created after a a peer review was requested.
Issues: it is the datetime of the newest first comment made after a peer review across all resolving pull requests. Resolving pull requests are pull requests that reference the issue via auto-closing keywords.
From: |
|
Github (PRs) | Calculated |
Gitlab (PRs) | Calculated |
Bitbucket (PRs) | Calculated |
JIRA | Inferred from PRs |
ClickUp | Inferred from PRs |
Trello | Inferred from PRs |
Reporting Use Cases
The First Comment After Review Requested At field is a specialized timestamp used to approximate the start of the active review process, particularly for GitLab, Bitbucket, and Azure DevOps, which do not have a formal review creation event like GitHub. It is crucial for accurately measuring the "idle time" of a pull request.
Calculating Review Idle Time: This field's primary purpose is to calculate the time a pull request waits before a reviewer starts actively engaging with it.
Time to First Review: You can measure your team's responsiveness to review requests with the custom formula
(first_comment_after_review_requested_at - review_requested_at) / HOUR(). A high average value for this metric is a strong indicator of a bottleneck at the beginning of your review process.
Filtering for Stale Review Requests: You can identify pull requests that are stuck waiting for a reviewer's first action.
Create a report of all open pull requests where a review has been requested but no one has started by using a filter where
Review Requested At is not nullandFirst Comment After Review Requested At is null. This helps you identify and unblock stalled work.
Creating Consistent Cross-Platform Metrics: For organizations using multiple Git providers, this field is essential for creating consistent cycle time metrics.
GitHub provides a more precise
First Review Created Attimestamp. To get a reliable "start of review" time across all platforms, you should use a formula that takes the earliest of the two available timestamps:LEAST(first_comment_after_review_requested_at, first_review_created_at). Using this formula as the starting point for your review phase calculations ensures your metrics are accurate regardless of the source tool.