Dataset: Issues & Pull Requests
Entity: Issues
Field ID: sub_type
Type: Text
Description: The type of issue, as seen in the source project management application (e.g., Story, Bug, Epic, Task, etc.). For pull requests, this field is always null
Source: App
Transformation logic: N/A
From: |
|
Github (PRs, Issues) | Use |
Gitlab (PRs, Issues) | N/A |
Bitbucket (PRs) | N/A |
Azure DevOps (PRs, Issues) | N/A |
JIRA (Issues) | Use |
ClickUp (Issues) | N/A |
Trello (Issues) | N/A |
Reporting Use Cases
The Sub-Type field is a crucial attribute for categorizing your work based on its official definition in your project management tool (e.g., Jira, Trello). It allows you to distinguish between "Bugs," "Stories," "Tasks," and "Epics," making it essential for analyzing where your team's effort is being allocated.
Filtering by Work Type: You can create highly focused reports by filtering on the issue type.
To build a dashboard focused solely on bug fixing, apply a filter where
Sub-Type = "Bug".To analyze all new feature development, you could filter where
Sub-Type equals any of "Story", "Epic".
Reporting and Workload Analysis: Using sub_type as a dimension is the best way to understand the composition of your backlog and your team's workload.
A pie chart with
Sub-Typeas the dimension andCOUNT()as the metric will instantly show the breakdown of your open issues.You can also compare performance metrics across different work types. A list report with
Sub-Typeas a dimension and a metric likeAVG(closed_at - created_at)can reveal if "Bugs" are resolved faster than "Stories."
Custom Formulas for High-Level Grouping: For even higher-level reporting, you can group similar sub-types together using a custom formula.
A formula like
IF(sub_type == "Bug" OR sub_type == "Hotfix", "Corrective Work", "Planned Work")can be used as a dimension to categorize your effort into broader business streams, simplifying your reports for a wider audience.