Unassigned Tasks counts items that exist in the team's queue without an assigned owner. It surfaces ownership and accountability gaps before they show up as missed deadlines.
What it measures
Total number of tasks in the team's projects with a null assignee field at the end of the selected period — covering both backlog and in-progress states.
How Leanmote calculates it
unassigned_tasks = count(items where assignee is null and status in (backlog, in_progress) at period_end)
Cancelled and done items are excluded.
Per-team rollup uses the team mapping on the project the task belongs to.
How to interpret it
Backlog unassigned is normal — most teams plan and assign just-in-time. Watch the trend, not the absolute number.
In-progress unassigned is a red flag — someone is presumably working on it but no one is accountable. Investigate immediately.
Growing unassigned counts week-over-week usually means planning isn't keeping up with intake.
What to do about it
Add an assignee step to your definition-of-ready or sprint-planning checklist.
Run a weekly grooming session that ends with every active item having an owner.
If a task can't be assigned because nobody owns it functionally, that's an org-design signal — escalate.
How it relates to other metrics
Unassigned tasks are excluded from all other metrics in Leanmote. Throughput, Cycle Time, Flow Efficiency, Reworked Tasks, Total Active Time, and every other performance metric only count tasks with an assigned owner. The Unassigned Tasks count is a dedicated signal — it does not silently inflate or distort any other number on your dashboard.
Related metrics
Assigned Tasks
Work in Progress (WIP)
Avg Age of Work in Progress