Issue Summary

Velocity chart's commitment points are not consistent with the values observed in Sprint report or the corresponding burndown chart for the sprint.

Steps to Reproduce

1. Cannot reproduce it consistently, but please refer to the screenshots.
   1. Test Sprint 4 started off with 13 story points initially.
   2. BurndownScreenshot:
       
   3. However, Velocity chart records an initial commitment of 8 points.
   4. VelocityChart: 
      
   5. BurndownChartDetails:
       
2. Similar to this, again, for sprint Test Sprint 10
   1. Started off with commitment story points of 9, as seen in the Burndown chart.
   2. burndownSprint10:
       
   3. This time, velocity chart shows the correct commitments though.
   4. VelocityChart: 
      
   5. BurndownChartDetails: 
      

Expected Results

An expected value for the Commitment story points should have been,

Commitment= SUM of Story Points (Issues Completed during the sprint + Issues Not Completed during the sprint + Issues Removed from the Sprint after it started)

That is, it should have considered the story points for ALL the issues which were present at the beginning of the sprint.

Actual Results

The values in the Velocity Chart are not correctly recorded, as corroborated by above screenshots. 

Workaround

Currently there is no known workaround for this behaviour. A workaround will be added here when available