Kanbus

Feature

Agile metrics

A metrics view in the console that counts issues by status, type, project and scope, using the same filters as the board.

Sometimes you want numbers rather than cards. The console's Metrics view summarizes the issues you are currently looking at: how many there are, where they sit in the workflow, and how they split across types, projects and local versus shared work. It reads the same live data as the board, so the counts change as issues change.

What it shows

Total and status

The number of issues in view, and a count for each status in your workflow, such as open, in progress, blocked and closed.

Type by status

Stacked bars for each issue type, split by status, which make a backlog of open or blocked bugs easy to spot.

Project and scope

Counts per project when virtual projects are configured, and shared versus local issue counts.

Filters carry over

Switch between Board and Metrics with the view toggle in the console header. Project filters, the local filter and other visibility controls stay active, and the metrics recalculate for that slice. Narrow to one project or hide local issues, and the totals and charts match what the board would show.

Reading the numbers

  • Many open issues with few in progress usually means work is queuing up.
  • A large blocked segment in one type can point at a dependency bottleneck.
  • An uneven project split shows where most of the delivery risk sits.
  • A growing local count is a reminder to promote work that is ready to share.

For counts in a terminal, kbs stats prints project statistics, and a wiki page can render status tables from the same data.

Learn more