Keypup

Dataset: Issues &amp; Pull Requests

Description: The open/close state of the item. Possible values are:

<code>CLOSED</code> the issue was closed or the pull request was closed without being merged.

<code>DRAFT</code> the pull request is currently being worked on and is not ready to be looked at by others.

<code>MERGED</code> the pull request was merged.

<code>OPEN</code> the issue or pull request is still active.

- <code>CLOSED</code> the issue was closed or the pull request was closed without being merged.
- <code>DRAFT</code> the pull request is currently being worked on and is not ready to be looked at by others.
- <code>MERGED</code> the pull request was merged.
- <code>OPEN</code> the issue or pull request is still active.

The <code>State</code> field is the most fundamental attribute for distinguishing between active and completed work, making it essential for virtually all reporting. As a text field with a fixed set of values (<code>OPEN</code>, <code>DRAFT</code>, <code>MERGED</code>, <code>CLOSED</code>), its primary use is for filtering, but it is also powerful as a dimension and within custom formulas.

Filtering for Workflow State: This is the most common use case for this field. You can scope any widget to a specific phase of the lifecycle.

- Active Work: To see all work that is still in progress, use a filter like <code>State = "OPEN"</code> or <code>State equals any of "OPEN", "DRAFT"</code>. This is the basis for any "current workload" or "backlog" report.
- Completed Work: To analyze historical performance, such as cycle time or throughput, you should filter for completed work using a filter like <code>State equals any of "MERGED", "CLOSED"</code>.
- Successful vs. Discarded Work: You can distinguish between work that was successfully delivered (<code>State = "MERGED"</code>) and work that was discarded without being merged (<code>State = "CLOSED"</code>), which is crucial for analyzing rework or wasted effort.

High-Level Health Monitoring: When used as a dimension, state provides an at-a-glance overview of your projects.

- A pie chart with <code>State</code> as the dimension and <code>COUNT()</code> as the metric will instantly show you the proportion of your work that is open, merged, or closed, providing a simple health check of your development pipeline.

Creating Advanced KPIs: You can use this field in <code>COUNT_IF</code> or <code>SUM_IF</code> formulas to create powerful performance metrics.

- Merge Rate: You can calculate the percentage of completed pull requests that were successfully merged (as opposed to being closed without a merge) with a custom formula like <code>ROUND(COUNT_IF(state == "MERGED") / COUNT_IF(state == "MERGED" OR state == "CLOSED") * 100, 2)</code>. A low rate might indicate that a lot of effort is being spent on work that is ultimately discarded.

- Filtering for Workflow State: This is the most common use case for this field. You can scope any widget to a specific phase of the lifecycle.
 - Active Work: To see all work that is still in progress, use a filter like <code>State = "OPEN"</code> or <code>State equals any of "OPEN", "DRAFT"</code>. This is the basis for any "current workload" or "backlog" report.
 - Completed Work: To analyze historical performance, such as cycle time or throughput, you should filter for completed work using a filter like <code>State equals any of "MERGED", "CLOSED"</code>.
 - Successful vs. Discarded Work: You can distinguish between work that was successfully delivered (<code>State = "MERGED"</code>) and work that was discarded without being merged (<code>State = "CLOSED"</code>), which is crucial for analyzing rework or wasted effort.
- High-Level Health Monitoring: When used as a dimension, state provides an at-a-glance overview of your projects.
 - A pie chart with <code>State</code> as the dimension and <code>COUNT()</code> as the metric will instantly show you the proportion of your work that is open, merged, or closed, providing a simple health check of your development pipeline.
- Creating Advanced KPIs: You can use this field in <code>COUNT_IF</code> or <code>SUM_IF</code> formulas to create powerful performance metrics.
 - Merge Rate: You can calculate the percentage of completed pull requests that were successfully merged (as opposed to being closed without a merge) with a custom formula like <code>ROUND(COUNT_IF(state == "MERGED") / COUNT_IF(state == "MERGED" OR state == "CLOSED") * 100, 2)</code>. A low rate might indicate that a lot of effort is being spent on work that is ultimately discarded.

Issues and PRs > State

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (PRs, Issues)	If `isDraft = true` then `DRAFT`. Otherwise, it is mapped from the `state` field: `CLOSED` => `CLOSED` `MERGED` => `MERGED` `OPEN` => `OPEN`
Gitlab (PRs, Issues)	If `draft = true` then `DRAFT` Otherwise, it is mapped from the `state` field: `closed` => `CLOSED` `merged` => `MERGED` `opened` => `OPEN`
Bitbucket (PRs)	Mapped from the `state` field: `DECLINED` => `CLOSED` `MERGED` => `MERGED` `OPEN` => `OPEN` `SUPERSEDED` => `CLOSED`
Azure DevOps (PRs, Issues)	If `isDraft = true` then `DRAFT` Otherwise, it is mapped from the `status` field: `abandoned` => `CLOSED` `active` => `OPEN` `completed` => `MERGED`
JIRA (Issues)	if `resolutiondate` is populated then `CLOSED`, otherwise `OPEN`.
ClickUp (Issues)	if `date_closed` is populated then `CLOSED`, otherwise `OPEN`.
Trello (Issues)	if `closed` OR `dueComplete` then `CLOSED`, otherwise `OPEN`.

Issues and PRs > State

Reporting Use Cases