Dataset: Issues & Pull Requests
Entity: Pull Requests
Field ID: resolved_issue_label_names
Type: List of text values
Description: The combination of labels from all resolved issues (via auto-closing keywords), deduplicated and sorted. It is only applicable to pull requests.
It can be used to get a quick overview of the type of work addressed by resolved issues (e.g., the field contains "critical-bug" and "medium-bug" labels, indicating that this issue was bundled with other bug fixes).
Source: Calculated
Transformation logic:
Pull Requests: Aggregate all results of
labelsfield from resolved issues. Identical labels are unified to prevent duplication. Resolved issues are issues that are referenced by a resolving pull request.Issues: Not applicable. This field will always be an empty array
[].
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | N/A |
ClickUp (Issues) | N/A |
Trello (Issues) | N/A |
Reporting Use Cases
The Resolved Issue Labels field provides the complete, combined list of labels from all issues a pull request resolves. This is incredibly powerful for categorizing and analyzing pull requests based on the original intent of the work, rather than just the labels applied to the PR itself.
Accurate Filtering by Work Type: This is the most reliable way to find pull requests related to specific types of work, especially for processes where labeling happens at the issue level.
Find All Bug Fixes: You can create a definitive report of all pull requests that address a bug by using a simple filter:
Resolved Issue Labels contains "bug".Track Epic/Feature Implementation: Monitor the progress of a large feature or epic by filtering for all pull requests that resolve issues with a specific epic label, for example,
Resolved Issue Labels contains "epic-new-auth-flow".
Analyzing Development Effort by Label: By using the
FLATTENfunction, you can see which types of issues (as defined by their labels) are generating the most development work.To visualize your team's effort, create a bar chart with the custom formula dimension
FLATTEN(resolved_issue_label_names)and aCOUNT()metric. This will show you how many pull requests were created for "bugs," "features," "tech-debt," and so on.
Custom Formulas for High-Level Grouping: You can create simplified, high-level reports by grouping various labels into broad categories that match your business logic.
A custom dimension with the formula
IF(CONTAINS(resolved_issue_label_names, "bug"), "Bug Fix", "Feature Work")can be used to create a pie chart that shows the proportion of your team's effort dedicated to fixing bugs versus building new features.