Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>resolution_state</code>

Description: An indication of whether the issue has been implemented via resolving pull requests or not. This is only applicable to issues. Pull requests will always have this field set to <code>NONE</code>. Resolution states can have the following values:

<code>NONE</code> the issue has no resolving pull requests or all the resolving pull requests have been closed (not merged).

<code>IN_PROGRESS</code> the issue has at least one open pull request resolving it.

<code>IMPLEMENTED</code> all the resolving pull requests have been merged.

- <code>NONE</code> the issue has no resolving pull requests or all the resolving pull requests have been closed (not merged).
- <code>IN_PROGRESS</code> the issue has at least one open pull request resolving it.
- <code>IMPLEMENTED</code> all the resolving pull requests have been merged.

Transformation logic: Indicates if an issue is currently being implemented by one or several pull requests or if all pull requests have been merged.

Issues and PRs > Resolution state

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, Issues)	N/A
Gitlab (PRs, Issues)	N/A
Bitbucket (PRs)	N/A
JIRA (Issues)	N/A
ClickUp (Issues)	N/A
Trello (Issues)	N/A