Dataset: Reviews
Entity: Pull Request Review
Field ID: submitted_at
Type: Datetime
Description: The datetime at which the review was submitted. Only GitHub may provide a value different from created_at (review started, resumed, then finished later). With other git platforms, reviews are instantaneous.
Source: App
Transformation logic: N/A
From: |
|
Github (Reviews) |
|
Gitlab (MRs) |
|
Bitbucket (PRs) |
|
Azure DevOps (PR Threads) |
|
Jira | N/A |
ClickUp | N/A |
Trello | N/A |
Reporting Use Cases
The Submitted At field from the Reviews dataset is the definitive timestamp marking the moment a reviewer finalizes and submits their feedback. It represents the completion of a single review cycle, making it essential for measuring review velocity, turnaround times, and overall throughput.
Measuring Review Throughput: The most common use of this field is to track the volume of completed reviews over time.
A line or column chart with a dimension like
YEAR_MONTH(submitted_at)and aCOUNT()metric creates a "Review Velocity" chart. This shows how many reviews your team is completing each month, which is a direct measure of your review capacity.
Calculating Review Durations: This field serves as the crucial "end" point for calculating how long different parts of the review process take.
Active Review Time (GitHub-specific): You can measure the time a reviewer actively spent on their review with the custom formula
(submitted_at - created_at) / HOUR().Reviewer Turnaround Time: To measure how long it takes a reviewer to act on a request, you can calculate the time from request to submission with
(submitted_at - requested_at) / DAY().
Filtering for Recent Activity: You can easily create reports that focus on recently completed reviews.
To build a "Weekly Review Digest" or to gather data for a retrospective, you can use a filter like
Submitted At in the previous 7 days.