Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolving_pr_label_names
Type: List of text values
Description: The combination of labels from all resolving PRs (via auto-closing keywords), deduplicated and sorted. It is only applicable to issues.
It can be used to get a quick overview of the type of work addressed by the resolving pull requests (e.g. the field contains "bugfix" and "hotfix" labels, indicating that this issue was addressed in a bug-fixing body of work).
Source: Calculated
Transformation logic:
Pull Requests: Not applicable. This field will always be an empty array
[].Issues: Aggregate all results of
labelsfield inherited from the PRs that resolve the issue. Identical labels are unified to prevent duplication. Resolving pull requests are pull requests that reference the issue via auto-closing keywords.
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 Labels field provides the complete, combined list of labels from all pull requests that resolve an issue. This allows you to analyze issues based on the characteristics and workflow of their associated implementation work, which is invaluable for understanding your development process.
Filtering by Implementation Context: You can create reports on issues based on the labels of the pull requests that fixed them.
Find Issues with "Hotfix" PRs: To identify all issues that were resolved by an urgent pull request, you can use a filter like
Resolving PR Label Names contains "hotfix".Analyze Work Involving Refactoring: Find all issues whose implementation included a refactoring effort by filtering where
Resolving PR Label Names contains "refactor".
Analyzing PR Label Usage from an Issue Perspective: By using the
FLATTENfunction, you can determine which pull request labels are most frequently associated with the resolution of issues.A bar chart with the custom formula dimension
FLATTEN(resolving_pr_label_names)and aCOUNT()metric can show you which PR labels are most common on the pull requests that complete your issues, revealing patterns in your development and review process.
Measuring Impact on Cycle Time: You can use the labels from the resolving PRs to segment your issues and compare their performance metrics.
For example, you can measure if issues resolved by PRs labeled as "complex" take longer to close. You could create a list widget with a custom dimension like
IF(CONTAINS(resolving_pr_label_names, "complex"), "Complex PR", "Standard PR")and a metric that calculates the average cycle time,AVG(closed_at - created_at). This helps you quantify the impact of complex implementations on your overall delivery timeline.