TM-11
CSV and HTML Issue Type Disagree
Type Misclassification
Default severity: medium
Product BacklogPrioritizationQualityBusiness Value
What it detects
import CSV type differs from HTML/snapshot type; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows import csv type differs from html/snapshot type; tests; catalogue during analysis.
- Example signal: import CSV type differs from HTML/snapshot type; tests; catalogue.
Suggested response
Retype or rewrite summaries so issue types match the actual work described.
Coaching playbook
Symptom
The "CSV and HTML Issue Type Disagree" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "CSV and HTML Issue Type Disagree" 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
Retype or rewrite summaries so issue types match the actual work described.
Facilitation questions
- What system change would stop "CSV and HTML Issue Type Disagree" 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.