What causes Commitment to be zero on my Velocity Chart?
I believe all Stories had Story Point values before Starting the Sprint. Also, my first sprint had a value in Commitment. I don't know what I did differently.
My Board is configured to use Points for Estimation Statistic and Remaining Estimate and Time Spent for Time Tracking.
I don't believe I was able to change previously completed sprints, but for all subsequent, I made sure my sprint start date and time was before any work (status change or hours logged) was done on sprint items.
Similarly when completing the sprint, make sure end date and time are after everything for the sprint has been updated in Jira.
Hope that helps.
Just wanted to help you out on this issue :) It sounds like you have added issues to your sprint after the sprint has begun. As discussed in https://confluence.atlassian.com/display/AGILE/Viewing+the+Velocity+Chart the 'Commitment' value is calculated on the issues and stories added before the start of the sprint.
A quick way to find issues or stories that were added after the sprint start is to view the Sprint Report. Issues that have a star next to the key were added after the beginning of the sprint.
To resolve the issue in future sprints you would create the sprint, add the issues from your backlog and then begin the sprint.
I had the same problem and here's how I solved it for a past sprint:
1) From the velocity report, go to the sprint in question from the list below the visual chart.
2) Reopen the sprint, from the options in the '...' menu on the right
3) Go to the backlog and edit the start time of this sprint to later than when the stories with asterisks* were added.
4) Close the sprint again.
Now the commitment will include all the stories with a time stamp before the start time you entered.
I just made sure all the items were part of the re-opened sprint (with starting time adjusted) at the point when I closed it again and it worked.
May be try it again, making sure the individual tickets are actually 'done,' as per their workflows...
Hey there, Benjamin.
Could there be an inconsistency in your JIRA instance that causes the values not being displayed properly? Have you tried to perform reindexing (https://confluence.atlassian.com/display/JIRA/Re-Indexing+after+Major+Configuration+Changes) to see if you still have the same issue? I am suspecting this since you mentioned that yor first sprint didn't suffer from this problem.
My Administrator submitted the question to Atlassian Tech Support and I believe the root cause is self-inflicted (I will confirm when completing my active Sprint Friday).
During Sprint Planning, we added Stories to the Sprint, with Story Points and then I Started the Sprint. However, after hitting Start Sprint, I changed the Start Time to the beginning of the day. Since the Stories had a later timestamp, they were consider added after the Start and thus not part of the Sprint Commitment.
Changing the Start Time of my Active Sprint (to after Sprint Planning completed) has already cleaned up my Burndown chart, so I'm hoping my Commitment value will be non-zero. If so, I will keep the default Start Time (current time) when Starting future Sprints.
Even though our sprints begins after we complete the sprint planning currently I have the project showing only commitment in the first sprint in the Velocity Chart, I have two additional sprint without commitment, any updates and/or hit to be able to register the sprint commitments?
Good Day, Bad bad traffic, not sure why!!!! 1/2 hour commute took me 2 hours today 🤯 What helped me is that I kept browsing LinkedIn until...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG