I'd like to be able to rely on the sprint report and velocity report data, but after much review, it is definitely not accurate. For now, I have been documenting my sprint "actuals" manually to combat this bug.  It is extra work that I really shouldn't have to do with a tool like JIRA and I hope this gets fixed soon!

Adding my vote. The Atlassian Knowledge Base page says "switch to the Burndown chart", which is far more information (and issues) than needed.

I've just commented in GHS-8776 so I won't repeat but it is the same issue and no progress seems to have been made despite all the comments!

Hi,
this is a very annoying bug but for the time being I have a workaround: when I need to set new estimation on a story already present in a sprint I simply clone the issue, set the story points, put the issue into the sprint and delete the old one. It may be problematic in case of issues with history that you still need, but you can still link new issues to the old ones.

Regards,
Maciej

Hello,

We are experiencing this phenomena, as well, and is casting a shadow of doubt on the accuracy of the velocity reports. We will have the affected teams adjust and make sure to not start sprints in JIRA until after all point values have been assessed, but going backward, I have to manually populate spreadsheets that contradict what someone else could pull up in JIRA.

Thanks in advance,

Steve

Hi,
Yes, but also on the sprint report a dash is displayed for story points for these tickets that get put in the sprint after the sprint has started.

On the Agile planning board, if you add story points to the story before moving it in, the value shows up on the planning board only. It doesn't get counted on the velocity report or displayed on the sprint report.

Regards,
Pat

Are you referring to the values listed on the Velocity Chart for Committed versus Completed?

This functionality makes sense once the sprint START date/time has passed, but if you make changes to points or move stories in or out of the sprint BEFORE the Start date/time well, that is just part of the planning process. The team 'commits' to what's currently in the sprint at the time of the Start Date/time. There should be a check on the Sprint start date when generating this report because otherwise, its just not accurate. Call it a bug or a design flaw, but the fact is that this report provides no value as it functions today.

_

Hi,
I agree with this. For stories added in after the sprint has started, their story points should be included in the committed count I feel and definitely shown in the Velocity Report. Having these story points not show up in the sprint or velocity reports really deflates what the team completed. Can this please be worked on cause it's kind of demoralizing to a team since the sprint and velocity charts don't depict the size of really what the team completed. On the flip side, it's correct not to include those stories that were removed into the story point count that was completed.

regards,
Pat