Original estimate of Burndown Chart can be wrong when work is logged on version start date without changing remaining estimate

Symptom

'Original Estimate' shown in Burndown chart may not correct for the specific date.

Cause

When work is log against issue on start date of version without remaining estmate is changed with it, that issue's estimate time may not be counted into the 'Original Estimate' shown in Burndown chart, because if there is any work logging in planning session (version start date), GreenHopper tries to catch the related remaining estimate after logging work to reflect the planned estimate, but it may run out of gear when failing to find it.

Workaround

Since this kind of work logging should be a rare scenario, adjusting version to start from the date before or after the current 'start date' may fix the burndown chart.