Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolution_state
Field Label: Resolution state
Type: Select list
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 NONE. Resolution states can have the following values:
NONEthe issue has no resolving pull requests or all the resolving pull requests have been closed (not merged).IN_PROGRESSthe issue has at least one open pull request resolving it.IMPLEMENTEDall the resolving pull requests have been merged.
Source: Calculated
Transformation logic: Indicates if an issue is currently being implemented by one or several pull requests or if all pull requests have been merged.
From: |
|
Github (PRs, Issues) | PRs: N/A |
Gitlab (PRs, Issues) | PRs: N/A |
Bitbucket (PRs) | N/A |
Azure DevOps (PRs, Issues) | PRs: N/A |
JIRA (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The Resolution State field is a powerful computed attribute that provides a clear, development-centric view of an issue's progress. Because it is automatically updated based on the status of linked pull requests, it is invaluable for tracking the true implementation status of your work, independent of manual updates to a workflow board.
Filtering for Accurate Workflow Stages: This field allows you to build highly accurate reports and Kanban boards that reflect real development activity.
"To Do" / Ready for Development: Create a list of all open issues that have not yet been started by filtering where
Resolution State = "NONE"."In Progress": Get a precise view of all issues currently being worked on by filtering where
Resolution State = "IN_PROGRESS"."Code Complete" / Ready for QA: This is a critical use case. You can identify all issues where the development work is finished (all PRs have been merged) but the issue itself is still open. A filter where
Resolution State = "IMPLEMENTED" and state = "OPEN"will create a list of items that are ready for the next step, such as QA, documentation, or release.
Reporting on Pipeline Health: Using
Resolution Stateas a dimension provides a clear snapshot of your development pipeline.A pie chart with
Resolution Stateas the dimension andCOUNT()as the metric can instantly show you the proportion of your open issues that are not started, in progress, or code-complete.
Measuring Implementation Rate: You can use this field to create KPIs that measure how effectively your team is translating planned work into active development.
A custom formula like
ROUND(COUNT_IF(resolution_state != "NONE") / COUNT() * 100, 2)can calculate the percentage of open issues that have development in progress, helping you understand how much of your backlog is being actively worked on.