Issues and PRs > Last review created at
Tom Azernour avatar
Written by Tom Azernour
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 pull request review submitted, from when the review was started. Only GitHub allows reviews to be started and finished later. GitLab and Bitbucket 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.

The table below maps the fields or logic from the source systems corresponding the most closely to the transformation carried out by Keypup:

From:

Github (PRs, Issues)

last_review_submitted.created_at

Gitlab (PRs, Issues)

Use the earliest updated_at of the request approvals endpoint.

Note: GitLab only exposes approved reviews, there is no concept of informational or “changes requested” reviews.

Bitbucket (PRs)

last_review_submitted.participated_on

JIRA (Issues)

Calculated from resolving PRs

ClickUp (Issues)

Calculated from resolving PRs

Trello (Issues)

Calculated from resolving PRs

Did this answer your question?