FI-03
Recurring Flag on Same Issue
Flags
Default severity: medium
ProcessOutputRisk
What it detects
A comment was added to a flagged issue explaining the impediment, but no subsequent comment from a different author (Scrum Master, manager, or peer) was added within the configured response window — the team acknowledged the problem but nobody responded or took action. flag_comments = comments.filter(created >= flag_set_date, issue=I)
Detection formula
IF COUNT(flag_comments) >= 1: first_comment = flag_comments\[0\] responses = comments.filter(created > first_comment.created, author != first_comment.author) IF COUNT(responses) = 0 AND (today - first_comment.created) > config.fi.response_window_days // default: 2 business days THEN FLAG no_response_to_flag IF (today - first_comment.created) > config.fi.critical_response_window_days // default: 5 days THEN CRITICAL — flag comment ignored for 5+ days Report: issue, flag_comment_text (first 100 chars), comment_date, days_without_response, assigneeExamples in practice
- A team shows a comment was added to a flagged issue explaining the impediment, but no subsequent comment from a different author (scrum master, manager, or peer) was added within the configured response window while response window days is set to 2 business days.
- Example signal: A comment was added to a flagged issue explaining the impediment, but no subsequent comment from a different author (Scrum Master, manager, or peer) was added within the configured response window — the team acknowledged the problem but nobody responded or took action.
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 explaining the impediment, but no subsequent comment from a different author (Scrum Master, manager, or peer) was added within the configured response window — the team acknowledged the problem but nobody responded or took action. flag_comments = comments.filter(created >= flag_set_date, issue=I)
Why it matters
When "Recurring Flag on Same Issue" 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 "Recurring Flag on Same Issue" 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.