Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: last_review_submitted_at
Type: Datetime
Description: The datetime at which the last review was submitted on a pull request. For issues, it is the timestamp of the newest review submission across all resolving pull requests.
Source: Calculated from pull request reviews
Transformation logic:
Pull requests: It is the submission datetime of the last pull request review
Issues: It is the submission datetime of the newest pull request 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) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | Inferred from PRs |
ClickUp (Issues) | Inferred from PRs |
Trello (Issues) | Inferred from PRs |
Reporting Use Cases
The Last Review Submitted At field is a critical timestamp that marks the conclusion of the active review and feedback phase. It is essential for calculating the total duration of the review cycle and for measuring the efficiency of the final handoff to the merge and deployment stage.
Calculating Total Review Cycle Duration: This field serves as the definitive end-point for the entire review and rework period.
You can measure the full "Review Time" with the custom formula
(last_review_submitted_at - LEAST(first_comment_after_review_requested_at, first_review_submitted_at)) / DAY(). This captures the entire duration from the moment the first review began until the very last piece of feedback was submitted, including any back-and-forth and rework commits.
Measuring Merge Time: This timestamp is also the starting point for the final "Merge Time" phase of a pull request's lifecycle.
The formula
(merged_at - last_review_submitted_at) / HOUR()calculates how long a pull request waits to be merged after all review activity has concluded. A high value for this metric is a strong indicator of a bottleneck in your deployment process.
Filtering for "Ready-to-Merge" Items: You can use this field to identify pull requests that have completed the review process but are waiting to be merged.
Create a report of all open pull requests by using a filter where
Last Review Submitted At is not null and Merged At is null. This creates a queue of items that are code-complete and reviewed, helping you focus on the final deployment step.