Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>first_comment_after_review_requested_at</code>

Description: The datetime of the first comment made after a peer review was requested. This timestamp may help identify when a peer review started for GitLab and Bitbucket, which do not support a formal review system. For GitHub, use the field <code>first_review_created_at</code> instead.

Pull requests: Datetime of the first comment created after a a peer review was requested.

Issues: it is the datetime of the newest first comment made after a peer 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: Datetime of the first comment created after a a peer review was requested.
- Issues: it is the datetime of the newest first comment made after a peer 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 > First comment after review requested 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 (PRs)	`first_comment_after_review_request.created_at`
Gitlab (PRs)	`first_comment_after_review_request.created_at`
Bitbucket (PRs)	`first_comment_after_review_request.created_on`
JIRA	N/A (see transformation logic)
ClickUp	N/A (see transformation logic)
Trello	N/A (see transformation logic)