Seriously? This is a super basic feature. This is a clear case of work that has HIGH VALUE for LOW EFFORT.

+1
It surprises me that this feature doesn't exist. The sprints' velocity data is there, why do we have to manually input these in the spreadsheet to get the average? Not to mention the velocity chart only displays the last 7 sprints..

+1 We need to be able to plan future work and know team velocity by sprint or release or timeframe based on all previous sprints. That should not have to be manually calculated by going to burndown charts and putting this data in a spreadsheet. I want average velocity over multiple past sprints

I think you should add an average line across the velocity report, and also added an average at the bottom of the table displayed underneath the chart.

Thanks for the link!

It's weird that the "work completed" in the "Release Burndown" doesn't match the information per sprint in the "Velocity Chart" (I'm talking about a Scrum board, of course).

We're not probably using the release/version in the proper way to achieve the correct results, but it's good to know for the future or different projects.

In a nutshell, I still need this feature of average velocity

It is documented at https://confluence.atlassian.com/jirasoftwarecloud/release-burndown-777002702.html

The report displays the velocity per sprint and the remaining work.

Hi Oscar, how can you use the Release Burndown report to get average velocity from last sprints?

I can see velocity per release, but I can't see any option for the average.

Thanks!

As a workaround, you can use the Release Burndown report which contains the velocity per sprint.

Just started looking into JIRA Agile reports and I was really surprised I couldn't find the average velocity of my team.

I've just started to learn JIRA and I am surprised there's no such useful feature for Agile as average velocity per any unit of time

This is a very basic feature for agile and I'd like to support the addition. It is very disappointing to see this take so long to be addressed. It often feels as though agile is tacked onto jira and secondary.

Managers want this value. There are all sorts of dashboards, but nothing that provides this simple value? Surprizing.

3 years and this isn't in? Why make us do the math when a simple "average" field can be tacked onto the Velocity Report?

+1 to getting this in. Seems like an easy and useful metric to calculate. Save me some time in spreadsheets.

It would definitely be useful to see how the average velocity is changing over time, especially for new agile teams as they go through storming, norming and performing.

I am wildly surprised this does not already exist! Would seem like a high value, low effort item to implement on the velocity chart. I also have to calculate this manually.

Not having this means that we have to manually compute this ourselves, which seems ridiculous since velocity over time is a standard part of the agile development process.

This is a very useful statistic that our development team utilizes within Pivotal. We are currently considering Greenhopper/Jira to replace Pivotal and this is surely something that the user will complain about!

Having the average velocity over the past week, month, year etc. displayed on the planning board as well would also be extremely useful during release planning. We often have users observing the planning process, and when committing to story points, we often have to stop and explain why we're committing to X number of story points.