Velocity/weekly throughput chart is not showing

[Raghu]

We are not able to see the Velocity/weekly throughput chart is not showing in the reports section.

Velocity Chart is not shown in Reports section.

Whether Velocity chart is applicable for Kanban board?

[Trudy Claspill · Accepted solution]

The Velocity Chart is not applicable to Kanban boards. Jira's native Velocity Chart uses Sprints as the time period for measuring velocity, and sprints are not used in Kanban.

If you want to see how many issues you are resolving on a weekly basis in a Kanban board you could use the Created vs. Resolved chart.

[Bill Sheboy]

Hi @Raghu -- Welcome to the Atlassian Community!

Yes, and...to Trudy's answer:

For teams using Kanban practices, and in my opinion, very few of the common/helpful measurements are supported (or supported well) by out-of-the-box by Jira.  Pause to consider what your team needs, and then perhaps try dashboard gadgets, building your own reporting from spreadsheet exports, or investigate the Atlassian marketplace for addon reporting.

Kind regards,
Bill

[Nic Brough -Adaptavist-]

Velocity is calculated from the time-boxes that Kanban does not have, so it cannot have a velocity. 

It looks instead at throughput, which the control chart is really good at displaying.  But Jira doesn't have a lot else for reporting Kanban, it's a bit weak (but then, in "pure" Kanban, all you really need is the control chart)

[Raghu]

Thanks Trudy, Bill and Nic for your reply.

[Emre Toptancı _OBSS_]

Hello @Raghu ,

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center. You can use this solution for all projects and boards. 

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. 

       

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

As an alternative solution, Time in Status also has Duration Between Statuses report type which shows the duration from issue creation to a specific status or the duration between two specific statuses.

  

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

Grouping issues by date parts will make it possible for you to get something very very similar to a velocity report and make a trend analysis.

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

And the app has a REST API so you can get the reports from Jira UI or via REST.

  

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 issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

https://marketplace.atlassian.com/apps/1211756/

EmreT

[Raghu]

Thanks Emre. Will check and get back to you.