Skip to main content

Issues and PRs > Last review created at

Tom Williams avatar
Written by Tom Williams
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Pull Requests, Issues

Field ID: last_review_created_at

Type: Datetime

Description: The datetime at which the last submitted pull request review was created. For issues, the timestamp is evaluated from resolving pull requests.

Source: Calculated from pull request reviews

Transformation logic:

  • Pull requests: It is the creation datetime of the last submitted pull request review. Draft reviews are ignored. Only GitHub allows reviews to be started and finished later. GitLab, Bitbucket, and Azure DevOps consider reviews as instant, meaning that last_review_created_at and last_review_submitted_at will always be equal.

  • Issues: It is the creation 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 Created At field is a timestamp that captures the moment the final review on a pull request was initiated. It is valuable for analyzing the efficiency and duration of the concluding stages of your review cycle.

  • Calculating Final Active Review Time: This field's primary use is to isolate and measure the time a reviewer actively spent on the last review before submission (GitHub only).

    • You can calculate this with the custom formula (last_review_submitted_at - last_review_created_at) / HOUR(). A long duration here might indicate that the final changes were complex, that the review was particularly in-depth, or that the reviewer was interrupted.

  • Filtering for Incomplete Final Reviews: You can identify pull requests where a reviewer may have started a final review but has not yet submitted it, which could indicate a blocker or an abandoned review (GitHub only).

    • Create a report of open pull requests filtered where Last Review Created At is not null and is significantly older than the Last Review Submitted At timestamp (or where the submission timestamp is still null). A filter like Last Review Created At before 2 days ago on an open PR that is still pending review can help spot these stalled final reviews.

Did this answer your question?