All Collections
Data & operations
Issues & Pull Requests dataset
Issues and PRs > First review submitted at
Issues and PRs > First review submitted at
Tom Azernour avatar
Written by Tom Azernour
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Pull Requests, Issues

Field ID: first_review_submitted_at

Type: Datetime

Description: The datetime at which the first review was submitted on a pull request. For issues, it is the timestamp of the oldest review submission across all resolving pull requests.

Source: Calculated from pull request reviews

Transformation logic:

  • Pull requests: It is the submission datetime of the first pull request review

  • Issues: It is the submission 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 (PR reviews)

first_review.submitted_at

Gitlab (PR reviews)

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 (PR reviews)

first_review.participated_on

JIRA (Issues)

N/A (see transformation logic)

ClickUp (Issues)

N/A (see transformation logic)

Trello (Issues)

N/A (see transformation logic)

Did this answer your question?