How to correct an incorrectly entered Original Estimate to prevent it from affecting reports

[Chris Addison]

We have a ticket that somehow had an Original Estimate given to it of over 2000h - I suspect it was a typo and was meant to be 2hrs or something. It was a ticket that had been created a while ago but we hadn't noticed the estimate discrepancy until recently when we were working on it.

We adjusted the Original Estimate to a sensible number but when we completed a Sprint we noticed that our charts like Burndown charts etc had become massively skewed because of the huge number that was originally there - and in the list of tickets at the bottom it still shows with the original high number.

The ticket is still in progress so has carried over the the next Sprint but in the reporting it is still using the initial value entered?

Is there any way to correct this?

[Tansu Akdeniz]

Hi @Chris Addison 

Since there is no option to delete history entry, it effects the chart visual.

Also, there is an open ticket related to it. Please watch and vote: JRASERVER-69002