OI-08
Operational Bucket Child Heap Size
Operational Issues
Default severity: medium
Product BacklogProcessMetrics
What it detects
An operational bucket parent issue (OI-01) accumulates a large heap of open child issues — the catch-all bucket has become an unmanaged backlog pile that inflates WIP counts, story-point commitments, and hides real delivery scope under a single umbrella parent.
Detection formula
IF issue flagged by OI-01: open_children = COUNT(child_issues WHERE status NOT IN config.workflow.done_statuses) open_child_sp = SUM(story_points, open_children) IF open_children >= config.oi.child_heap_open_count_threshold // default: 15 THEN FLAG child_heap_size IF open_child_sp >= config.oi.child_heap_open_sp_threshold // default: 40 SP THEN FLAG child_heap_size IF open_children >= count_threshold * 2 OR open_child_sp >= sp_threshold * 2 THEN CRITICAL Report: open_child_count, open_child_sp, list of oldest open childrenExamples in practice
- A team shows an operational bucket parent issue (oi-01) accumulates a large heap of open child issues while done statuses is set to Configured per workspace.
- Example signal: An operational bucket parent issue (OI-01) accumulates a large heap of open child issues — the catch-all bucket has become an unmanaged backlog pile that inflates WIP counts, story-point commitments, and hides real delivery scope under a single umbrella parent.
Suggested response
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Coaching playbook
Symptom
An operational bucket parent issue (OI-01) accumulates a large heap of open child issues — the catch-all bucket has become an unmanaged backlog pile that inflates WIP counts, story-point commitments, and hides real delivery scope under a single umbrella parent.
Why it matters
When "Operational Bucket Child Heap Size" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Facilitation questions
- What system change would stop "Operational Bucket Child Heap Size" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.