BH-07
Cancellation Without Documentation
Backlog Health
Default severity: medium
Product BacklogPrioritizationRiskEffort
What it detects
An issue was cancelled without a comment explaining why — cancellation decision is invisible and prevents learning.
Detection formula
cancelled_resolutions = config.workflow.cancelled_resolutions // e.g. \[\'Won\'t Do\', \'Cancelled\', \'Invalid\'\] IF issue.resolution IN cancelled_resolutions AND COUNT(comments WHERE text_length > config.backlog.min_cancellation_comment_length) = 0 // default: 20 chars THEN FLAG Compute: documented_cancellation_rate per team (positive metric)Examples in practice
- A team shows an issue was cancelled without a comment explaining why while cancelled resolutions is set to Configured per workspace.
- Example signal: An issue was cancelled without a comment explaining why — cancellation decision is invisible and prevents learning.
Suggested response
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Coaching playbook
Symptom
An issue was cancelled without a comment explaining why — cancellation decision is invisible and prevents learning.
Why it matters
When "Cancellation Without Documentation" 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
Refine or prune ageing, imbalanced, or inconsistently closed backlog items.
Facilitation questions
- What system change would stop "Cancellation Without Documentation" 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.