Average Flow Chart / Mesure Flow in Kanban

Question

I want to measure the flow in a Kanban board.

We use the average age report and have a filter on only issues which have the stati "selected", "in progress" and "in review" and are "stories", "tasks" or "bugs" (epics have been excluded). But the chart takes the diff. between creation and resolve day. But this is not a good metric as many tasks may be planned in the backlog.

Zoryana Bohutska _SaaSJet_ · Answer

Hi @Andreas Geißinger

Also, you can try alternative solutions from Atlassian Marketplace like :

- Time in Status for Jira Cloud (by SaaSJet) - lets create status group for calculation the sum of time spent in flow statuses and total time spent on each issue. Additionally, this add-on has chart views for reports and gadget for Jira Dashboard.

- Time Between Statuses - lets you monitor each step in the workflow or total flow time by setting start/stop/pause statuses for calculation the configuration menu. Also, plugin allows set time limits and notification for exceeded issues.

Hope this information will help you

Best Regards

Zoryana

Emre Toptancı [OBSS] · Answer

Hello @Andreas Geißinger ,

The Cumulative Flow Diagram and especially Control Chart that are available in Kanban Board Reports might give better insight. Control Chart especially (with some limited configuration) can show times for a group of statuses. The downside is, it does not show individual issues and it is not possible to get averages in the way you want.

Our team at OBSS built Time in Status app for similar needs.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee (and much more). You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype.)

You can also combine durations of multiple statuses into consolidated columns to see metrics like Cycle Time or Lead Time.

The app has custom calendar support so you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Using Time in Status you can:

* See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
* Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
* Export your data as XLS, XLSX or CSV.
* Access data via REST API.
* See Time in Status data and charts for each issue as a tab on issue view screen.

Timepiece - Time in Status for Jira

EmreT