FI-01
Flag Without Resolution Action
Flags
Default severity: medium
ProcessOutputRisk
What it detects
A flag has been active on an issue for longer than the configured maximum flag age — the impediment was raised but never resolved. Long-lived flags indicate either the impediment is not being addressed or the flag was forgotten after raising. Measured in calendar days from flag set to today (or flag removal date). flag_set_date = changelog.find(field=\'flagged\', new=\'Impediment\', LATEST).date flag_age_days = (today OR flag_removal_date) - flag_set_date
Detection formula
IF flag_age_days > config.fi.max_flag_age_warning_days // default: 5 business days THEN FLAG long_lived_flag IF flag_age_days > config.fi.max_flag_age_critical_days // default: 10 business days THEN CRITICAL — impediment has been open for 2+ working weeks without resolution Report: issue, flag_set_date, flag_age_days, assignee, status, last_comment_dateExamples in practice
- A team shows a flag has been active on an issue for longer than the configured maximum flag age while max flag age warning days is set to 5 business days.
- Example signal: A flag has been active on an issue for longer than the configured maximum flag age — the impediment was raised but never resolved.
Suggested response
Close the loop on flags—link blockers, set owners, and clear impediments with traceability.
Coaching playbook
Symptom
A flag has been active on an issue for longer than the configured maximum flag age — the impediment was raised but never resolved. Long-lived flags indicate either the impediment is not being addressed or the flag was forgotten after raising. Measured in calendar days from flag set to today (or flag removal date). flag_set_date = changelog.find(field=\'flagged\', new=\'Impediment\', LATEST).date flag_age_days = (today OR flag_removal_date) - flag_set_date
Why it matters
When "Flag Without Resolution Action" 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 Without Resolution Action" 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.