Are others seeing incorrect values in the Release Burn down story point totals?

[Desiree Leslie]

The total story points for a sprint does not equal the accumulated points showing for the items in the sprint.  In the picture below, Sprint 39 is showing correctly, but sprint 38 is not.  The total story points are 19 for sprint 38 and it's showing 21.  I'm not sure where the additional 2 story points are coming from.  There wasn't any mid-sprint story point change, so I'm not sure why there would be a difference.

[Jim Constant]

I noticed the same thing and I believe it's counting story points of issues that are resolved or closed during the sprint. And when I say 'resolved or closed' in this context, I mean issues that you've actually completed as well as any you've decided not to do for some reason so you resolve or close them.

For the Release Burndown report, I think JIRA is establishing a total number of story points for the release (the scope) and that number is fixed. Then anything that happens to stories after that is reflected in the Story Points number of each sprint regardless of why it's closed. If you do the story, it counts. If you close the story because you're not going to do it, it counts. If you remove the Fix Version, it counts. 

There appears to be different behavior for the Version Report. If you remove or change the Fix Version of a issue, the scope of the version goes down.

This is my theory based on some testing and am hoping Atlassian will confirm.

[Troy Spetz]

We use JIRA 7.12 server version.

Is it possible that one/more of your issues was assigned to 2 sprints? 

If so, I think the points assigned to the issue are included in both sprint SP totals.

JIRA assumes that all issues assigned to a sprint -- are also completed in the same sprint (i.e. no issue carry-over).