FI-06
Flagged Item Aging Beyond Cycle Time Threshold
Flags
Default severity: medium
ProcessOutputRisk
What it detects
The same issue has been flagged more than once — the impediment was raised, cleared, and then the issue became blocked again. Recurring flags on the same issue indicate the root cause was not resolved, a workaround was applied instead of a fix, or the issue is structurally blocked and should be removed from the sprint.
Detection formula
FOR each_issue I: flag_cycles = COUNT(changelog WHERE field=\'flagged\' AND new=\'Impediment\', issue=I) IF flag_cycles >= config.fi.recurring_flag_warning_count // default: 2 THEN FLAG recurring_impediment IF flag_cycles >= config.fi.recurring_flag_critical_count // default: 3 THEN CRITICAL — same issue flagged 3+ times; structural blocker unresolved Report: issue, flag_cycles, flag_dates, resolution_comments (or lack thereof) per cycleExamples in practice
- A team shows the same issue has been flagged more than once while recurring flag warning count is set to 2.
- Example signal: The same issue has been flagged more than once — the impediment was raised, cleared, and then the issue became blocked again.
Suggested response
Close the loop on flags—link blockers, set owners, and clear impediments with traceability.
Coaching playbook
Symptom
The same issue has been flagged more than once — the impediment was raised, cleared, and then the issue became blocked again. Recurring flags on the same issue indicate the root cause was not resolved, a workaround was applied instead of a fix, or the issue is structurally blocked and should be removed from the sprint.
Why it matters
When "Flagged Item Aging Beyond Cycle Time 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 "Flagged Item Aging Beyond Cycle Time 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.