OI-01

Operational Tracker Issue — Summary Signal

Operational Issues

Default severity: medium
Product BacklogProcessMetrics

What it detects

An issue\'s summary matches configured operational/administrative tracker patterns — terms like \'Operativa\', \'Operation\', \'Zberne\', \'Evidence\', \'Admin\', \'Tracking\', \'Catch-all\'. These issues are used for logging operational work in Jira rather than representing deliverable features or stories. They severely distort lead time (they often stay open for months), cycle time, WIP counts, and throughput metrics. They must be detected and either excluded from flow metrics or reclassified.

Detection formula

operational_keywords = config.oi.operational_keywords // defaults (EN): \[\'operativa\', \'operation\', \'operational\', \'admin\', \'administration\', \'tracking\', \'catch-all\', \'catchall\', \'bucket\', \'container\', \'generic\', \'misc\', \'miscellaneous\', \'general\', \'various\', \'ongoing\', \'continuous\', \'running\', \'permanent\', \'standing\'\] // defaults (SK/CZ): \[\'operatíva\', \'operativa\', \'zberné\', \'zberne\', \'evidencia\', \'evidenčné\', \'prevádzka\', \'administratíva\', \'všeobecné\', \'priebežné\', \'bežné\', \'operačné\'\] IF summary MATCHES any(operational_keywords) CASE_INSENSITIVE OR description MATCHES any(operational_keywords) CASE_INSENSITIVE (first line only) THEN FLAG operational_tracker CRITICAL if: issue has been open > config.oi.max_operational_age_days // default: 30d Report: issue, age_days, time_logged, impact on team metrics if excluded

Examples in practice

  • A team shows an issue\'s summary matches configured operational/administrative tracker patterns while operational keywords is set to see 5n.2.
  • Example signal: An issue\'s summary matches configured operational/administrative tracker patterns — terms like \'Operativa\', \'Operation\', \'Zberne\', \'Evidence\', \'Admin\', \'Tracking\', \'Catch-all\'.

Suggested response

Separate operational trackers from product flow or exclude them consistently from delivery metrics.

Coaching playbook

Symptom

An issue\'s summary matches configured operational/administrative tracker patterns — terms like \'Operativa\', \'Operation\', \'Zberne\', \'Evidence\', \'Admin\', \'Tracking\', \'Catch-all\'. These issues are used for logging operational work in Jira rather than representing deliverable features or stories. They severely distort lead time (they often stay open for months), cycle time, WIP counts, and throughput metrics. They must be detected and either excluded from flow metrics or reclassified.

Why it matters

When "Operational Tracker Issue — Summary Signal" 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 Tracker Issue — Summary Signal" 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.

Product tourSign in
OI-01: Operational Tracker Issue — Summary Signal — FlowAnalyzer