This feature has finished rolling out to 100% of production users, and is currently rolling out in the release tracks schedule.

Agreed as per below!

Hi, it's really basic to see the average velocity (what's the point of velocity if i can't see the average...). please add it 

this ticket is open for 11 years... it has almost 500 voters (if you include all the votes in the duplicate) and you have the functionality in DC. So it sounds really small but valuable. please considering addressing it soon

+1 please

In our company we have several teams using the velocity as a tool to plan what we can take into a sprint and make forecast for our product development.
Having the number calculated by Jira as default would help so much, as today we have let's say somehow a variety in how the velocity is calculated.
This feature would decrease manual work and gives a company an easy way to standardize the velocity calculation.

Maybe more than 10 years of having this open will come to an end soon. I press the thumbs

+1

Hopefully this will come about soon. Can you add this functionality too:

As a Scrum Master, I would like to pick the number of past Sprints (e.g. 3 Sprints or 6 Sprints) the average velocity is calculated over, so that I have the flexibility of choice for different Teams.

Thanks!

+1

Come on Atlassian, it's 11 years already

We need this in Jira Cloud please!

TIMEFRAME: A GIVEN PERIOD > APPLY!

Thanks, Chris.

Please add this tiny thing again. This will make feel Jira Cloud less sh... sorry attliassian, I miss my server.

This is natively available in Jira Server and very useful for reporting. Please consider adding to Jira Cloud. 

I think providing the average velocity for the team would be beneficial to help them plan more effectively.

+1 please! 

+1000

+

I think providing the average velocity for the team would be beneficial to help them plan more effectively.

1+

Would like this update please

You are right, it is paid: Great Gadgets by StonikByte

I don't think so. We got this for free: https://community.atlassian.com/t5/Jira-Software-articles/Tracking-scope-changes-and-unplanned-work-with-Insights-for-Jira/ba-p/2237140

The velocity gadget mentioned in the previous comment is only available with a paid 3rd party plugin.

We still need this feature in native Jira Cloud.

I've found the average velocity is available in the velocity gadget on Jira dashboards.

Same here, waiting for this feature!

It will be really helpful to have this feature as without that average trend line, velocity chart doesn't make much sense. It was really efficient in demonstrating statuses across all the forums. Kindly acknowledge this request. 

It's better not to offer Velocity Report on cloud than offering a velocity report without Average velocity over a period of time .......
Velocity report is almost useless without these two features. 

We just migrated from Server to cloud this week and the two most useful features in the Velocity Reports were removed(or not built on cloud) ; Average Velocity and Time Range (3, 6, 12,custom) .   How are we supposed to calculate average velocity over a year at scale w/out these features? 

Being able to isolate a given sprint on the Velocity Report gives Scrum Masters and Product Owners a more accurate view of WIP; without a day-to-day view giving accurate commitments to other teams is challenging. 

We also need this same functionality in Cloud like it was in Server.

Looking for this as well as I was used to having it on Jira Server

I need to calculate the velocity for my team over the past year as holidays and other leave balance out over the year so this is useful for getting an accurate number of story points per sprint. 

We just migrated from the old Jira Server to the cloud and it was very shocking to find that this feature doesn't exist in the cloud version. 

Echoing comments that the reports page is worthless without a calculated average.

As a PM, I want to know my team's average velocity, so I can assign a sane number of tickets per sprint — and avoid over-allocating. Especially for weeks when I know there are holidays or people are on vacation, it's extremely easy to over-allocate.

As this already exists in Jira Server, it should exist in Cloud as well, presuming that it was added to Server because there already was interest.

Having average velocity in the velocity chart is what makes the data useful. There should be a filter for sprint duration so you only compare like time periods when generating the average.

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.

It would be really useful to have this information, but surprisingly it's not available.

I'm thinking about building an app to automate this, as I have different teams needing this info, but I'd be great if Atlassian can do the magic for us.

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.