Assigned Tasks counts the items currently assigned to a team or member, regardless of which workflow state each item is in. It's a snapshot of the workload someone is carrying — backlog, in progress, and waiting all included.
What it measures
The number of items assigned to this team or member whose sprint falls inside the selected period, plus the items with no sprint at all. A task assigned to someone but sitting in a sprint outside the window does not appear, so this is not a full snapshot of everything they carry.
How Leanmote calculates it
assigned_tasks = count(items where assignee = member and (sprint in period or sprint is null))
Includes every state — to-do, in progress, in review, blocked, etc.
Items finished or unassigned during the period are excluded. If a task loses its assignee, it drops out of Assigned Tasks and will appear in Unassigned Tasks instead.
Per-team value is the sum across all members on that team.
How to interpret it
High Assigned Tasks with low WIP usually means a deep backlog of unstarted work — common and not necessarily a problem.
High Assigned Tasks with high WIP means active overload. Start fewer things.
If Assigned Tasks differs sharply from Throughput and the member has been stable, work may be stuck or scope may be inflated.
What to do about it
Re-balance during planning if one person's queue is materially larger than others'.
Pair with WIP — if WIP is fine but Assigned Tasks is huge, the issue is just queue depth.
Look for stale items in the assignee's queue. Big assigned counts often hide forgotten tickets.
Related metrics
Work in Progress (WIP)
Throughput
Avg Member WIP Age
Team Overview tab — what each metric tells you