Velocity Chart - Original Estimate and Time Remaining

[Aman Sawrup]

Hi All.

My question is about how "Commitment" is computed for Jira issues which are incomplete and moved to the next sprint. 

Let's say I have an issue whose "Original estimate" is 4d and then in "Time tracking" 2d is logged as "Time spent" meaning "Time remaining" is 2d.  When the sprint is completed and the issue is incomplete and moved over to the next sprint, will the "Commitment" for the following sprint for the issue be 2d (Time remaining) or 4d (Original estimate)?

Thanks.

[Dave Mathijs]

Hi @Aman Sawrup welcome to the Atlassian Community!

The burndown chart is calculated on the Original Time Estimate (if you don't choose Story Points or Issue Count).

[Aman Sawrup]

Hi @Dave Mathijs. Thanks for the info.  In the case of an incomplete issue, how should I handle it?  Should I reduce the Original Time Estimate to the Time Remaining before completing the sprint?  

[Dave Mathijs]

That's up to you of course. Personally, I would keep it as it is because when you complete the issue in the next sprint, you'll complete an issue with that original estimate, even if you spent x hours of it in the previous sprint.

[Aman Sawrup]

But won't that cause the Velocity to be incorrect for the next sprint?  It will say 4d of work got completed when in fact it was only 2d.

[Dave Mathijs]

The velocity counts for the active sprint. The issue wasn't completed in the previous sprint, so no increase in the velocity in the previous sprint.

[Aman Sawrup]

Right but for the next sprint, the Completed value will be increased by 4d instead of 2d.  I think this will cause the Velocity value to be incorrect.

This would be fixed if the Commitment used Time Remaining instead of Original Time Estimate for incomplete Jira issues that were carried forward from the previous sprint.