Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>review_approved_at</code>

Description: The datetime at which a pull request first met its minimum approval quota from approving reviews. For issues, it is the oldest approval timestamp from resolving pull requests.

Source: Calculated from pull request reviews

Pull requests: It is the submission datetime of the first review that allowed the pull request to meet its minimum number of approving reviews to be considered approved. The minimum number of approving reviews is a configuration parameter that is usually available in each git project. If none was configured, Keypup considers that the minimum number of approving reviews is 1. Note that pull requests will not be considered as “approved” while there is a “request changes” review still active, even if the number of approving reviews reaches the minimum number of approving reviews. The “request changes” review must be discarded or re-requested for review first.

Issues: It is the oldest “approved at” datetime 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 review that allowed the pull request to meet its minimum number of approving reviews to be considered approved. The minimum number of approving reviews is a configuration parameter that is usually available in each git project. If none was configured, Keypup considers that the minimum number of approving reviews is 1. Note that pull requests will not be considered as “approved” while there is a “request changes” review still active, even if the number of approving reviews reaches the minimum number of approving reviews. The “request changes” review must be discarded or re-requested for review first.
- Issues: It is the oldest “approved at” datetime 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:

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