OI-03
Operational Issue Used as Worklog Container
Operational Issues
Default severity: medium
Product BacklogProcessMetrics
What it detects
An operational tracker issue has significant hours logged against it — the team is logging real work time against an evidence/umbrella issue rather than against specific deliverable items. This makes effort invisible at the feature/story level, distorts time-spent metrics, and prevents accurate estimation and capacity planning.
Detection formula
IF issue flagged by OI-01: total_logged = SUM(worklog.time_spent, issue) IF total_logged > config.oi.worklog_container_threshold // default: 8h (1 full day) THEN FLAG worklog_container authors = DISTINCT(worklog.author, issue) IF COUNT(authors) > 1 THEN CRITICAL (multiple people logging to umbrella issue) Report: total_logged, author_count, list of worklog authors, date range of worklogs Recommendation: create specific sub-issues and relog time properlyExamples in practice
- A team shows an operational tracker issue has significant hours logged against it while worklog container threshold is set to 8h (1 full day).
- Example signal: An operational tracker issue has significant hours logged against it — the team is logging real work time against an evidence/umbrella issue rather than against specific deliverable items.
Suggested response
Separate operational trackers from product flow or exclude them consistently from delivery metrics.
Coaching playbook
Symptom
An operational tracker issue has significant hours logged against it — the team is logging real work time against an evidence/umbrella issue rather than against specific deliverable items. This makes effort invisible at the feature/story level, distorts time-spent metrics, and prevents accurate estimation and capacity planning.
Why it matters
When "Operational Issue Used as Worklog Container" 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 Used as Worklog Container" 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.