FI-15

Flag Raised After Configured Issue Age Threshold

Flags

Default severity: medium
ProcessOutputRisk

What it detects

A comment was added to a flagged issue but is shorter than the configured minimum length — the \'comment\' is too short to describe the impediment, who is affected, or what is needed. Single-word or emoji responses do not constitute actionable impediment descriptions.

Detection formula

FOR each_flag_comment C: IF len(C.text.strip()) \< config.fi.min_comment_length // default: 50 characters THEN FLAG superficial_flag_comment IF len(C.text.strip()) \< config.fi.critical_min_length // default: 20 characters THEN CRITICAL — comment is effectively empty Actionable flag comment should include: what is blocked, who or what is causing it, what is needed to unblock Report: issue, comment_text, comment_length, author

Examples in practice

  • A team shows a comment was added to a flagged issue but is shorter than the configured minimum length while min comment length is set to 50 characters.
  • Example signal: A comment was added to a flagged issue but is shorter than the configured minimum length — the \'comment\' is too short to describe the impediment, who is affected, or what is needed.

Suggested response

Close the loop on flags—link blockers, set owners, and clear impediments with traceability.

Coaching playbook

Symptom

A comment was added to a flagged issue but is shorter than the configured minimum length — the \'comment\' is too short to describe the impediment, who is affected, or what is needed. Single-word or emoji responses do not constitute actionable impediment descriptions.

Why it matters

When "Flag Raised After Configured Issue Age Threshold" 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

Close the loop on flags—link blockers, set owners, and clear impediments with traceability.

Facilitation questions

  • What system change would stop "Flag Raised After Configured Issue Age Threshold" 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
FI-15: Flag Raised After Configured Issue Age Threshold — FlowAnalyzer