CH-11

Priority Changed Repeatedly

Content & History

Default severity: medium
Product BacklogProcessQuality

What it detects

Issue priority was changed more than the configured warning and critical thresholds. priority_changes = changelog.filter(field=\'priority\')

Detection formula

IF COUNT(priority_changes) >= config.content.priority_change_warning // default: 3 THEN FLAG IF COUNT >= config.content.priority_change_critical // default: 5 THEN CRITICAL

Examples in practice

  • Stable after refinement
  • A team shows issue priority was changed more than the configured warning and critical thresholds while priority change warning is set to 3.
  • Example signal: Issue priority was changed more than the configured warning and critical thresholds.

Suggested response

Protect narrative quality: write items before work starts and avoid late or empty edits.

Coaching playbook

Symptom

Issue priority was changed more than the configured warning and critical thresholds. priority_changes = changelog.filter(field=\'priority\')

Why it matters

When "Priority Changed Repeatedly" 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

Protect narrative quality: write items before work starts and avoid late or empty edits.

Facilitation questions

  • What system change would stop "Priority Changed Repeatedly" 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
CH-11: Priority Changed Repeatedly — FlowAnalyzer