Issue Summary

This is reproducible on Data Center: Yes

Steps to Reproduce

a) Create a sprint
b) Add 3 issues with 5 story points each
c) Start the sprint
d) During the course of the sprint, change the issue type of one story issue to bug. Ensure that the bug is estimated via the original estimate and not story points
e) Complete the sprint

Currently the burndown chart model only uses the column change history and estimate history to derive its data. For this to work it will need to know the Issue type history to be able to determine whether a burndown event (column change) was valid for the particular estimate at the time and should be counted. Also you will need the issue type history to be able to add scope change events for when the issue was changed to an estimable or not estimable type.

Expected Results

There should be no discrepancy from post changing the issue type.

Actual Results

The burndown chart shows the story points (5) estimated for the bug issue (previously story) as well.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available