We've had this same issue when re-estimating story point values for features which weren't completed (or started) during our sprint. When planning the new sprint we added the features that weren't completed, changed the estimates and then noticed the velocity chart had a lower commitment that completed. After changing the story point estimate back to the original value, the sprint report still shows '-'s in place of the esimate. Any news on a fix or workaround?

I have ben experiencing this issue on our sprints created after Aug 23 and I have not found a way to avoid it and it is causing me major headaches for reporting. What I do not understand why some story point values show correctly and others have the (--) displayed. All stories were entered and committed to before starting the sprint. Can Jira provide an explanation? or a fix?

I have the same issue here.

I started print on 8/27 with story points and completed the sprint on 9/10.

The story points are missing the sprint report shown as "-".

I created other sprints a few weeks ago and started one new sprint on 9/10, will these sprints have the same issue or not?

If yes, how can i avoid this from happening again?

Yes this looks like a bug that we are tracking in the linked issue.

We started using Jira in August of 2013 for our projects and has no issues with our Sprint Reports showing the the story points completed and not completed until after Sprint 3 which was started on Aug 12 and completed on Aug 23. In this Sprint 3 all point values displayed correctly in the our Sprint Report and Velocity report. (see attached Sprint 3 report). However, we noticed when we completed Sprint 4 the report had missing story points as well as Sprint 5. (see attached). We always have the team commit the stories prior to starting the sprint and we never add stories after the sprint started. So can someone tell what is going on, can this be a bug that was introduced by the recent Jira upgrade? Please reply, I need a fix to this and fast.

The issue with the dash is a Bug not a Story, even though you listed in the reproduction steps that both are stories. In the vanilla configuration, you cannot add story points to bugs. Perhaps you were mistaken when you thought you added the story points? The screenshots show nothing wrong, and the documentation you listed about the asterisk has nothing to do with the dash - the asterisk is by the issuekey when an issue is added AFTER sprint start. See the attached screenshot.