Hilbana
ES/EN

Insights

Workspace flow metrics: cycle time, WIP and throughput, by week or by month.

On video

  • How long does a task really take?
  • Who closes more, your team or your agents?

Insights is the flow-metrics dashboard for the whole workspace, computed from issues and their state-change history.

What it shows

  • Cycle time (average and median): days between an issue first entering a started state and reaching completed.
  • WIP (work in progress): issues currently in a started state.
  • Completed: total within the chosen window.
  • Projects: the workspace portfolio. One row per project with work left or activity in the last 30 days, with its progress (done out of total, with a bar), the tasks in review and not started, the pace (tasks per working day over the last 10 weekdays), the estimated end, the share of reopened (reopenings ÷ closings: how much work goes back) and the last activity. Sort by progress, estimated end, activity or name, filter by project label, and each row takes you to the project’s Team tab, which shows the same figures.
  • Throughput per period: bars with issues completed per week or per month.
  • By person / agent: a table with each assignee’s completed count and average cycle time (unassigned appears separately).

You can switch the granularity between day, week and month. The daily view shows the last 14 days: how many tasks were closed, sent to review and reopened each day and who did it, and below it a summary by person with their working days and the hours logged (if you use time tracking). You can narrow it to one project or one project label. They’re the same counts as the “By day” table in each project’s Team tab, added up.

Details worth knowing

  • The portfolio is only for workspace members: a guest on a project doesn’t see it. It counts each project’s tasks; what an initiative delivers to a product counts in the initiative. The estimated end is a linear extrapolation (Monday to Friday, no holidays): if the pace changes, so does the date.

  • Cycle time is measured even if the issue was completed outside the window: it reflects the historical pace. A reopened issue stops counting as completed.

  • Throughput and the per-person breakdown only count what was completed within the window.

  • What counts as started or completed is decided by the state’s category, not its name, and sums the equivalent states across all teams.

Related: Workflow states · Cycles · Issues.