Velocity Charts not showing committed story points correctly

[Denis Haramincic]

Hi everyone.
Does anyone have experience with cleaning up velocity charts in Jira?
In a agile project committed story points are accumulated randomly.  Since 3 or 4 sprints the values are incorrect and won't rejust. It seems the number for committed story points will be continue to accumulate itself.
How can the velocity chart in Jira be retroactively cleaned up and set right?
Thanks for help and advices. We generate overall report out if it. 

[Nic Brough -Adaptavist-]

Welcome to the community!

Could you explain what you think is wrong with this chart?  And what you expect it to be doing?

[Denis Haramincic]

What is wrong on this chart is that committed story points continue to accumulate.

The amount of Sprint 13 should be 25 Story Points, and for Sprint 14 30 Story Points.

[Nic Brough -Adaptavist-]

I do not understand what you think is wrong with the chart?  The chart is trying to show you how your story points are being dealt with, sprint to sprint.

The chart is telling me that the committed points are rising because you're committing to more and more in your sprints.

[Denis Haramincic]

Correct, so the chart can only be interpreted incorrectly.

The committed Story Points should be cleared up after completion in 12.4. The amount of committed story points in the chart does not correspond to the actual committed story points.

[Nic Brough -Adaptavist-]

Ok, the "clear up" is not what the chart is trying to show you. 

It's trying to show you what you committed to and later delivered against.   If you spend a bit of time with a calculator, you'll see the grey bar is, for each sprint, "all committed points - the resolved points in green".  It doesn't go down if you de-commit from issues, because you committed to them.

[Denis Haramincic]

Thank you for the answer. In general, that would be correct and good if it showed exactly these stories for the committed story points.

In our chart, the value for the committed user stories is no longer correct from Sprint 13 onwards. The chart seems to continue to accumulate the values of past Stories. The commit takes place for each sprint individually and should not arbitrarily accumulate Story Points

[Nic Brough -Adaptavist-]

Yes, but that's what the chart is supposed to be showing you - the accumulating commitment over time, alongside what you're delivering.

[Denis Haramincic]

To date, no sprint-related obligations have accumulated over time. The bar would go up and down depending on how many Story Points were committed in the sprint. But in Sprint 13, the bar grows arbitrarily

[Heather Rommel [HyperVelocity]]

I know it's been a while, but I was researching something else and came upon this post. I've seen this kind of thing happen if someone modifies the workflow and forgets to set the Resolution field to either mandatory if the user is filling it out or adding the Post Function to auto-set the Resolution on a "done" status.