CH-13
Description Content Removed Mid-Flight
Content & History
Default severity: medium
Product BacklogProcessQuality
What it detects
Description was reduced by more than the configured shrinkage threshold after the issue entered active status — information was removed from an active issue. description_versions = changelog.filter(field=\'description\', date > first_active_date).sort(date)
Detection formula
FOR consecutive versions (v1, v2): IF v2.length \< v1.length * config.content.description_shrinkage_threshold // default: 0.5 (50% reduction) THEN FLAG content_removalExamples in practice
- Filled before activation; grows over time
- A team shows description was reduced by more than the configured shrinkage threshold after the issue entered active status while description shrinkage threshold is set to 0.5 (50% reduction).
- Example signal: Description was reduced by more than the configured shrinkage threshold after the issue entered active status — information was removed from an active issue.
Suggested response
Protect narrative quality: write items before work starts and avoid late or empty edits.
Coaching playbook
Symptom
Description was reduced by more than the configured shrinkage threshold after the issue entered active status — information was removed from an active issue. description_versions = changelog.filter(field=\'description\', date > first_active_date).sort(date)
Why it matters
When "Description Content Removed Mid-Flight" 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 "Description Content Removed Mid-Flight" 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.