Issue Summary

The burndown insight displays incorrect "points to go" value, and can drop below 0 on the y-axis.

Steps to Reproduce

This is easier to explain with an example, imagine this is the board column mapping

Note: There is an Unmapped status named "Ideation".

1. Create an issue and move it to the "Ideation" status, and give this an estimation i.e. 5 story points.
2. Create another issue in "To Do" status, , and give this an estimation i.e. 3 story points.
3. Add both issues to the sprint
4. Start the sprint
5. Move the "Ideation" status from the "Unmapped statuses" column to the "To Do" column.
6. Open the Insights panel on the board, and view the Burndown insight.

Actual Results

The issue that is in the "Ideation" status, does not have its estimation value reflected in the "points to go" value or the chart.

Note: As a consequence of this, once all issues in the sprint move to done, the burndown insight can go negative.

Expected Results

The issue that is in the "Ideation" status, does have its estimation value reflected in the "points to go" value or the chart.

Workaround

To fix this issue a recalculation needs to be triggered.

• First, map the status (as described above in step 5)
• Then, edit the sprint and change either sprint start or end date. Recommend moving the end date 1 minute later. This will trigger a recalculation and should now include the estimation from the issue that is in the status that was previously unmapped.