Velocity chart showing zero in commitment

[Ivan_He]

For some reason the commitment in the velocity chart is showing as zero. Attaching a snap shot of the chart. As you can see it was showing in previous sprints but not for sprint 8. Also happened another time (sprint 6) 

I did some research and could not find out why. Any thoughts on what might be the issue? 

Below is a screen shot of the commitment not showing up (sprint 6 and 8)

[Ivan_He]

Thanks for the feedback @Trudy Claspill . I do remember that my team and I had estimates for all of our tixs when we started the new sprint.

I think what could be happening is that I'm using a custom start and end date. I'm setting the time for the custom start date to be in the past.

Example:

11/9 - Finished sprint planning at 2pm EST

11/9 - Close out finished sprint at 2:15pm EST

11/9  - At 2:20p EST, I start the new sprint on with a time of 12am EST (in the past). 

[Trudy Claspill]

Hello @Ivan_He 

I tried that myself and I believe you are correct. I started a sprint and set the start time to a time earlier in the day. After closing the sprint, the Committed value in the Velocity chart was 0.

I recommend that you open a support case directly with Atlassian about this, and find out if this is a known or unknown bug, or intentional functionality.

https://support.atlassian.com/contact/#/

Please post back here with their response.

[Trudy Claspill]

@Ivan_He 

Did you pursue this topic with Atlassian Support? If so, what was their response?

[Trudy Claspill]

Hello @Ivan_He 

Welcome to the community.

A zero value in the Committed bar for the Velocity chart indicates that there was no estimation information entered for issues in the sprint at the time the sprint was started.

You would need to look at the history of each issue and compare when the estimation information was entered for each issue against the date/time the sprint was started.