Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>required_approval_count</code>

Description: The number of approvals this pull request requires before it can be considered approved. For issues, the value is calculated from resolving pull requests.

Source: App (Pull requests) / Calculated (Issues)

Pull Requests: use the approval settings from the source application. It is defaulted to 1 if null (no approval settings configured).

Issues: sum the required approvals of 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: use the approval settings from the source application. It is defaulted to 1 if null (no approval settings configured).
- Issues: sum the required approvals of 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>.

Issues and PRs > Required approvals

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)	`branchProtectionRule. requiredApprovingReviewCount`
Gitlab (PRs)	`merge_request_approvals. approvals_required`
Bitbucket (PRs)	None
JIRA (Issues)	Calculated from resolving PRs
ClickUp (Issues)	Calculated from resolving PRs
Trello (Issues)	Calculated from resolving PRs