After changing 'Original Estimate' the Sprint Report is still showing the first 'Original Estimate'. It's nonsensical as long as it's permissible to change 'Original Estimate'.
..Or is my reasoning wrong?
Your Original Estimate is locked down at the point you start your sprint - until that point any changes on scope automatically update the Original Estimate. Once you start the sprint then changes to Estimate are recorded but do not alter the Original Estimate as this was locked down but do impact the scope to be completed in the sprint. When you view the burndown chart for instance you will see these changes reflected in the red line showing the remaining work. Scope added to the sprint will cause the redline to go up, whilst scope removed will cause it to drop. However, the grey line of the predicted completion which was calculated using your original estimate will not alter.
The reasoning behind this is that a team is committing to deliver a certain amount of scope in the Sprint and this is reflected in the Original Estimate - it is expected that changes in scope during a sprint will be minimal and most frequently be the swapping of similar size stories (but only ones that have not yet been started) where a new dependency is identified.
I hope this helps explain the logic behind what you are seeing.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs