Dataset: Issues & Pull Requests
Entity: Pull Requests
Field ID: resolved_issue_sub_types
Type: List of text values
Description: The combination of sub-types from all resolved issues (via auto-closing keywords), deduplicated and sorted. It is only applicable to pull requests.
Source: Calculated
Transformation logic:
Pull Requests: Aggregate all results from the
sub_typefield of resolved issues. Sub-types are sorted and deduplicated for consistency reasons. 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 Sub-Types field is an essential attribute for accurately categorizing your engineering work based on its original definition in your project management tool (e.g., Jira). By providing a list of issue types like "Story," "Bug," or "Task" associated with a pull request, it allows for precise analysis of where your team's effort is being spent.
Filtering by Work Type: This is the most reliable way to create reports focused on a specific category of work.
Isolate Bug Fixes: To see all pull requests that address bugs, you can create a filter where
Resolved Issue Sub-Types contains "Bug".Analyze Feature Development: To focus on new features, you can filter for pull requests that resolve stories with
Resolved Issue Sub-Types contains "Story".
Reporting on Effort Distribution: To get a clear breakdown of your team's workload, you must use the
FLATTENfunction to analyze each sub-type individually.Work Breakdown Chart: You can create a pie or bar chart showing the proportion of pull requests dedicated to each issue type. Use a custom formula dimension like
FLATTEN(resolved_issue_sub_types)with aCOUNT()metric to visualize this distribution. This is crucial for understanding how much time is spent on new features versus maintenance or bug fixes.
Advanced Performance Analysis: You can use this field to compare performance metrics across different types of work.
Cycle Time by Work Type: To see if bug fixes are resolved faster than new features, you can create a list report with
FLATTEN(resolved_issue_sub_types)as the dimension andAVG(merged_at - created_at)as a metric. This can reveal important patterns about your team's priorities and processes.