Issues and PRs > First review created at

Dataset: Issues & Pull Requests

Entity: Pull Requests, Issues

Field ID: first_review_created_at

Type: Datetime

Description: The datetime at which the first 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 first 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 first_review_created_at and first_review_submitted_at will always be equal.
Issues: It is the creation datetime of the oldest 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)	`first_review_submitted.created_at`
Gitlab (PRs, Issues)	Use the earliest `updated_at` of the request approvals endpoint. Note 1: GitLab only exposes approved reviews, there is no concept of informational or “changes requested” reviews. Note 2: GitLab does not expose a submission timestamp per approval, only a timestamp indicating when the approvals endpoint was last updated. Keypup does its best to keep track of timestamps for successive approvals but those will be tracked accurately only after merge requests have been imported into Keypup.
Bitbucket (PRs)	`first_review_submitted.participated_on`
JIRA (Issues)	Calculated from resolving PRs
ClickUp (Issues)	Calculated from resolving PRs
Trello (Issues)	Calculated from resolving PRs

Issues and PRs > First review submitted at

Issues and PRs > Review rejected at

Issues and PRs > Review approved at

Issues and PRs > Review last approved at

Issues and PRs > Last review created at