-
Suggestion
-
Resolution: Fixed
-
195
-
12
-
-
Currently the Velocity Chart is hardcoded to show (max) last 7 sprints. Looking at the average amount of work completed in a sprint is the main value of the Velocity Chart, so the value of the Velocity Chart increases with every sprint, because the average is getting better.
If you have Sprint of two weeks length, you are talking about only 3-4 months. If vacation or christmas time is in between, you average is getting poor.
Therefore the limitation to show only last 7 sprints is bad and should be removed.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
- relates to
-
- Closed
-
![[Atlassian Support System]](/images/icons/generic_link_16.png "[Atlassian Support System]")
GHS-5942
You do not have permission to view this issue
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-6034] Velocity Chart should show all Sprints and not be limited to last 7 Sprints
I am using Jira cloud velocity chart, and I am still restricted to last 7 sprints. How/where is this feature changed please.
Dear,
Could you help me to see all sprint in my Jira now, I still see only 7 sprints even my project has more than sprints.
Thanks so much,
This Server ticket is closed (dead).
Proper complaints should go to the Cloud version here:
Please implement this asap on cloud version, I can't understand why it isn't already or why it initially was limited to only 7!
+1 to add to cloud. Also can we have story/ticket velocity please...
I see this fix came out a long time ago. Do you need to reach a certain number of sprints to be available? Currently, I am unable to modify the velocity chart to filter for a specific time range.
Thanks.
Is this available in Jira Cloud yet? I'm not seeing any option to show more than 7 sprints.
Agreed with Jeff and Rowann above.
It is disappointing indeed that none of the features are ever fixed on cloud first.
ALthough this is fixed in server, why are we still gathering interest for clous separately?
Should this not be part of the process to fix things for both cloud and server even if not cloud first?
90fd802dab6a, this issue is closed because it refers to Server only. JSWCLOUD-6034, which is the Cloud equivalent, is still open and gathering interest. It's also the one that the Cloud team would monitor for questions and feedback.
Why is the issue Closed? It still is not available in Cloud. Is there an ETA? It is really disappointing how JIRA Cloud is so behind. Isn't the benefit of it being Cloud based is that we're on the latest version? How is Atlassian not keeping the Cloud version up-to-date?
Hi 3306b41b2cc3, JSWCLOUD-6034 is the source of truth about the Cloud plans for this issue, and the best place to raise interest in it.
Any chance there is an ETA for this fix for the Cloud version of JIRA? This is a feature that would be of a great help 
2cc550efc68d I'm sorry, this is only a server feature for the moment - to increase the chance of creating something similar in cloud, let them know that you want it here: https://jira.atlassian.com/browse/JSWCLOUD-6034
stevepinell Filtering sprint by sprint is not a part of this update, but it sounds like your problem might be solved by the recent feature "Viewing options" -> "Hide unrelated sprints". Let me know if that's the case.
Wooo!!! Awesome news! Gets me away from manual Google Sheet scripting/reporting!
If possible and if it's not too much to ask, could we also include the ability to remove sprints from this report if we wish to exclude it for any reason - if this is not included as part of this enhancement of course?
For a specific example, today, if anyone accidentally sets a sprint on a card for sprint unrelated to one of the teams I work with in our Jira Instance, that sprint will be made visible in the velocity report and could obfuscate the velocity calculations made available as part of this new feature. Adding the ability to simply remove the sprint (with acknowledgment / confirmation if may not be available in the report at a later date or providing the ability to also add a sprint to the report at a later date to mitigate sprints being removed in error) would address this concern.
I know this will more than likely be resolved with the separate feature (if the enhancement is made available at a later date) being reviewed on https://jira.atlassian.com/browse/JSWSERVER-10805, but this will still be a problem until the referenced enhancement is also made available.
This is awesome! Eagerly awaiting the release. Is it going to be available for Next Gen Jira Cloud users?
Hey guys, I was able to achieve what I need via EazyBI.
Perfectly showing what I need.
Apparently not. We have release cycles that go more than 7 sprints, and are having trouble identifying at Release End all Jira's that were added after sprint start--a super handy statistic that I haven't found a way to get out Jira other than through the Velocity Chart. Ridiculous that @Atlassian has had this open for so long...
This request was created 8 years ago, not sure why Jira doesn't provide such simple and useful function.
I second Max Clendenning's comment!!!Unable to render embedded object: File ( Adding the requested flexibility to the Velocity Chart should be simple task and would make life SO much easier. Get with it Atlassian) not found.!!
"In progress" for 16 months!? I can't imagine that flexibility at any company I've ever worked at. Must be nice.
Sure would be encouraging to get a meaningful update on issues that are so ancient yet heavily upvoted.
It'd be helpful to have a date range or a sprint(s) picker. Allow users the option to see what they wanna see in the [Velocity chart]& not limit to the last seven sprints or the entire history of sprints for that matter.
Prashant, I think your situation is the same as Inka's, i.e. it sounds like you should separate your 4 Scrum Teams by Boards on the project. This would give you, in the short term, 7 Sprints per Team as they would each have their own Velocity Chart (because a board will separate those reports as well).
However, just to add to this ticket, I too think it's a good idea to make the number of Sprints that are visible on a Velocity Chart to be configurable. To some Teams, "all Sprints" would be interesting, to others, only the last few matter (as it's more of an indicator of the team's current trajectory, IMO).
The Version Report and Release Burndown should be clarified to indicate how many Sprints they are using for their projections though. IMO, that would round out the feature that this ticket would be a part of.
We are having 4 scrum teams and velocity chart showing 7 sprints which is not even 2 sprints each for the team. It is practically of no use. Can this be configurable to specify number of sprints to be included in velocity chart?
@inka.benthin
It sounds like what you may actually need to do first is to separate your 3 teams on to 3 separate boards on the same project. That will allow you to see 3 separate velocity charts, one per team.
You also may need to start researching Jira Portfolio and Jira Align in planning how to scale your use of Jira to meet your organizational needs.
Hope that helps.
For scaled scrum this is neccessary.
Currently we have three teams, so we see only last two sprints.
That makes the report almost useless.
Every time I look for something simple with Jira, I find an issue that dates back 7+ years. It's almost like the entire business plan has rolled to broken out of the box, and force users to buy another addon from the marketplace to fix it.
Maybe they should use a tool to keep track of the progress on this ticket? 
The status field in the description above indicates that this was in Progress as of October 2018. What is the current status? Was this released? Is it close? What is the estimate for release?
We are using parallel sprints and report of 7 iterations is really uncomfortable. Is it planned to increase the current limit?