TQ-21
Description Image or Attachment Stub Only
Text Quality
Default severity: high
ProcessMetrics
What it detects
Description points to screenshot or attachment without searchable text (~5.8% antipattern).
Detection formula
IF description matches see-screenshot/attachment stubs with minimal prose THEN FLAGExamples in practice
- Viď screenshot v prílohe — no acceptance criteria in body.
Suggested response
Write acceptance-oriented text in the ticket; attach media as evidence only.
Coaching playbook
Symptom
Description points to screenshot or attachment without searchable text (~5.8% antipattern).
Why it matters
When "Description Image or Attachment Stub Only" 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
Write acceptance-oriented text in the ticket; attach media as evidence only.
Facilitation questions
- What system change would stop "Description Image or Attachment Stub Only" 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.