OI-04
Operational Issue Without Subtasks — Flat Structure
Operational Issues
Default severity: medium
Product BacklogProcessMetrics
What it detects
An operational tracker issue exists without any child sub-tasks or linked items — the team is logging all operational work to a single parent issue with no breakdown. This makes the work completely opaque: what was actually done is invisible, and the time logged cannot be attributed to any deliverable.
Detection formula
IF issue flagged by OI-01: IF COUNT(child_issues) = 0 AND COUNT(linked_issues WHERE type IN config.oi.task_link_types) = 0 AND issue.time_spent > config.oi.min_hours_for_structure_check // default: 4h THEN FLAG flat_operational_issue Recommendation: decompose into specific sub-tasks per activity type; log time against sub-tasksExamples in practice
- A team shows an operational tracker issue exists without any child sub-tasks or linked items while task link types is set to 4h.
- Example signal: An operational tracker issue exists without any child sub-tasks or linked items — the team is logging all operational work to a single parent issue with no breakdown.
Suggested response
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Coaching playbook
Symptom
An operational tracker issue exists without any child sub-tasks or linked items — the team is logging all operational work to a single parent issue with no breakdown. This makes the work completely opaque: what was actually done is invisible, and the time logged cannot be attributed to any deliverable.
Why it matters
When "Operational Issue Without Subtasks — Flat Structure" 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 Issue Without Subtasks — Flat Structure" 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.