velocity report- why commitment is different than the original estimations in the the sprint report?

[Keren Hacohen Zada]

on the sprint report: I accumulate the left number that represent the original estimations at sprint start from all 3 categories: Completed Issues, Issues not Completed, Issues Removed From Sprint. 

it does not match the Commitment in the velocity report

[Dan -minware-]

Disclaimer: marketplace partner!

Hey @Keren Hacohen Zada 

I see that you figured out the answer to you question but if you are interested in analyzing work that was added after the start of a sprint and open to marketplace partners I would like to invite you to check out minware.

You can see the burn up chart below that clearly shows the impact tickets added or removed from the start had on work-in-progress and you would simply expand the "Completed - Added After Start" to dig in:

We try to make things as simple as possible so anyone on your team can understand how ticket flow impacts WIP.

Good luck finding what you are looking for, I hope this helps!

[Keren Hacohen Zada]

thank you

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Have you done something like adding sprint estimates to non-sprint items (like sub-tasks)?

[Keren Hacohen Zada]

i figured it out, In Velocity report, the committed is exactly what we had at Sprint start. if we added estimates or scope and did not complete it, it will not be counted at all. 
the completed is exactly what we have at sprint end- meaning, regardless if it was there at sprint start or added later, if it's completed- it's counted