Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolving_pull_request_sysids
Type: List of text values
Description: The list of pull request System IDs (Keypup IDs) that resolve an issue via auto-closing keywords.
It can be used to:
Count the number of resolving pull requests on each issue
See a list of resolved issues from a specific pull request by configuring a drilldown report on the resulting values (select all issues where the resolving pull request IDs contain the selected PR ID).
Source: Calculated
Transformation logic:
Pull Requests: This field will always be an empty array
[]Issues: The list of system IDs (Keypup-generated IDs) from resolving pull requests.
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | N/A |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The Resolving PR IDs (System) field is the technical link that connects an issue to the pull request(s) that implement its solution. It is essential for understanding how work is broken down and for analyzing the scope and complexity of your development efforts from the issue's perspective.
Filtering for Process Adherence: You can create reports that segment your issues based on their implementation status, which is determined by this link.
Identify Unstarted Work: To find all open issues for which no development work has started, you can use a filter where
Resolving PR IDs (System) length = 0. This is a core component of identifying your "To Do" or "Ready for Development" backlog.Find Multi-PR Issues: Isolate complex issues that required more than one pull request to be resolved by filtering where
Resolving PR IDs (System) length > 1. This can help you identify work that was either large in scope or required follow-up fixes.
Measuring Implementation Complexity: The most powerful use of this field is to quantify the amount of development effort (in terms of PRs) an issue required.
You can calculate the average number of pull requests needed to resolve a single issue with the custom formula
AVG(LENGTH(resolving_pr_sysids)). A high number might indicate that your issues are large epics, while a number close to 1 suggests a one-to-one relationship between issues and pull requests.