Task Analytics
Task Analytics answers three questions about your organisation's work: who is behind, on what, and whether the team is keeping up. Open it from Task Analytics in the Tasks group of the left menu.
Controls
| Control | Options |
|---|---|
| Scope | Everyone (every task in the organisation) or Me (only tasks assigned to you). |
| Window | 7 days, 30 days or 90 days. The default is 30. It applies to everything that says "in the window". |
| Refresh | Reloads the numbers. |
Archived tasks are never counted.
The summary tiles
Seven tiles run across the top. Click any tile to jump to the matching tasks on the Tasks page (or My Tasks when the scope is Me).
| Tile | What it counts |
|---|---|
| Open | Every task that is not Completed, whenever it was created. |
| Overdue | Open tasks whose due date has passed. A due date runs to the end of the chosen day, so a task due today is not overdue until tomorrow. Turns red when above zero. |
| Due this week | Open tasks due today or in the next six days. |
| Completed | Tasks completed inside the window. The line under the number says how many were created in the same window, for example "in 30d · 122 created", so you can see whether you are closing work as fast as it arrives. |
| On time | Of the tasks completed in the window that had a due date, the share completed on or before it. The line under it shows the counts, for example "2 of 4". Tasks with no due date are left out; if there are none you see "no dated completions". The tile turns amber below 70%. |
| Cycle time | The median number of days from a task being created to being completed, across tasks completed in the window. "median of 28" tells you how many tasks it is based on. |
| Unassigned | Open tasks nobody owns. |
Charts
Throughput. A line chart of tasks created against tasks completed, one point per day across the window. If completed stays under created for weeks, your backlog is growing.
By status. How many live tasks sit in each status.
By severity. For each severity, how many tasks are open and how many of those are overdue.
Workload
A table of open work by person, sorted by most open first. Click any column heading to sort; click a row to open that person's tasks on the Tasks page. Tasks assigned to a group are counted against the group.
| Column | Meaning |
|---|---|
| Person | The assignee. A row called Unassigned collects tasks with no owner. |
| Open | Not completed. |
| In progress | Currently in the In progress status. |
| Overdue | Open and past due. |
| Completed | Completed inside the window. |
| Points | The total points of the tasks that person completed inside the window. |
| Share of open | A bar showing that person's part of all open work. |
Needs attention
Three short lists of up to ten tasks each. Click the list title to open the full set in the Tasks list; Open in the list at the bottom of the page does the same for all tasks.
| List | Contents |
|---|---|
| Overdue | Open tasks past their due date, oldest due date first. |
| Going stale | Open tasks whose last update was 14 days ago or more. |
| Unassigned & severe | Critical or High tasks with no owner. |
How to read it
- A rising Overdue with a flat Unassigned means owned work is slipping; look at Workload for who is overloaded.
- A rising Unassigned means intake is outrunning triage. Assign in bulk from the Tasks page.
- On time falling while Cycle time stays flat usually means due dates are being set unrealistically, not that the team is slower.
- A long Going stale list is often a sign of tasks that were created "to remember" and never owned. Archive what no longer matters.
Good to know
- Points are whatever your team enters. Use them consistently or ignore the column.
- Cycle time uses the median, so a single very old task does not distort it.
- Numbers describe the tasks as they are now. There is no history of past states: if you re-open a completed task it leaves the Completed count.
- To hand the numbers to someone outside Hunto, use the browser's print function or a screenshot; Task Analytics has no export button. See Use cases and wiring tips for an "SLA ageing report" recipe using an export from the API.