TQ-23

Description Communication Diary or Email Dump

Text Quality

Default severity: high
ProcessMetrics

What it detects

Description is a communication diary, status log, or forwarded email (~2.8% / 0.5% mail dump).

Detection formula

IF email headers, multiple dated log lines, or forwarded-message markers THEN FLAG

Examples in practice

  • 2024-01-05 update: … 2024-01-12 update: … with no stable requirement block.

Suggested response

Extract decisions and requirements; move thread history to comments.

Coaching playbook

Symptom

Description is a communication diary, status log, or forwarded email (~2.8% / 0.5% mail dump).

Why it matters

When "Description Communication Diary or Email Dump" 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

Extract decisions and requirements; move thread history to comments.

Facilitation questions

  • What system change would stop "Description Communication Diary or Email Dump" 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
TQ-23: Description Communication Diary or Email Dump — FlowAnalyzer