Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>review_rejected_at</code>

Description: The datetime at which a pull request was first rejected after a review (“changes requested”). For issues, it is the timestamp of the oldest rejection review across all resolving pull requests.

Source: Calculated from pull request reviews

Pull requests: It is the submission datetime of the first pull request review with the status “request changes”.

Issues: It is the submission datetime of the oldest “request changes'' review across all resolving pull requests. Resolving pull requests are pull requests that reference the issue via <a href="https://docs.keypup.io/en/articles/8117180-linking-pull-requests-to-issues">auto-closing keywords</a>.

- Pull requests: It is the submission datetime of the first pull request review with the status “request changes”.
- Issues: It is the submission datetime of the oldest “request changes'' review across all resolving pull requests. Resolving pull requests are pull requests that reference the issue via <a href="https://docs.keypup.io/en/articles/8117180-linking-pull-requests-to-issues">auto-closing keywords</a>.

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

Issues and PRs > Review rejected at

Find answers and get help from Intercom Support and Community Experts

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

From:
Github (PR reviews)	`first_rejection_review.submitted_at`
Gitlab	`first_rejection_review.created_at`
Bitbucket (PR reviews)	`first_rejection_review.participated_on`
JIRA	N/A (see transformation logic)
ClickUp	N/A (see transformation logic)
Trello	N/A (see transformation logic)