IT-08

Concentrated Bug Filing Burst

Issue Type Distribution

Default severity: medium
Product BacklogMetricsQuality

What it detects

Multiple defects linked to the same feature (or filed by the same reporter when unlinked) were created within a short window — batch discovery after deferred testing. Complements IT-02 sprint-level bug spikes with per-feature or per-reporter concentration.

Detection formula

FOR each_feature F OR reporter R: bugs_in_window = COUNT(bugs WHERE created within config.it.bug_burst_window_days AND (linked_to F OR reporter=R)) IF bugs_in_window >= config.it.bug_burst_min_count // default: 3 THEN FLAG concentrated_burst Report: scope, bug_count, window_days, bug keys

Examples in practice

  • A team shows multiple defects linked to the same feature (or filed by the same reporter when unlinked) were created within a short window while bug burst window days is set to 3.
  • Example signal: Multiple defects linked to the same feature (or filed by the same reporter when unlinked) were created within a short window — batch discovery after deferred testing.

Suggested response

Rebalance issue-type mix and debt trends so quality signals stay intentional.

Coaching playbook

Symptom

Multiple defects linked to the same feature (or filed by the same reporter when unlinked) were created within a short window — batch discovery after deferred testing. Complements IT-02 sprint-level bug spikes with per-feature or per-reporter concentration.

Why it matters

When "Concentrated Bug Filing Burst" 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

Rebalance issue-type mix and debt trends so quality signals stay intentional.

Facilitation questions

  • What system change would stop "Concentrated Bug Filing Burst" 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
IT-08: Concentrated Bug Filing Burst — FlowAnalyzer