FL-04
Unassigned Active Issues
Flow
Default severity: high
ProcessMetricsOutputRisk
What it detects
Issues of the configured types in active statuses have no assignee.
Detection formula
IF issue.type IN config.workflow.owner_required_types // e.g. \[Epic, Feature\] AND issue.assignee IS NULL AND issue.status IN config.workflow.active_statuses THEN FLAGExamples in practice
- Board policy limits are exceeded or status movement patterns look artificial.
- Work piles up in one column or moves in bulk instead of flowing steadily.
- A team shows issues of the configured types in active statuses have no assignee while owner required types is set to Configured per workspace.
Suggested response
Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.
Coaching playbook
Symptom
Issues of the configured types in active statuses have no assignee.
Why it matters
When "Unassigned Active Issues" 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
Inspect board policy, WIP, and status hygiene so flow matches how work actually progresses.
Facilitation questions
- What system change would stop "Unassigned Active Issues" 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.