As a user, I would like the time estimates of new issues added during the middle of a sprint to be reflected as a spike in the burndown chart.

Sometimes during the course of a sprint, there are new tasks that need to be added that were not known during sprint planning. When we create new issues to represent these tasks, we assign a time estimate (under the "original time estimate" field). The problem is that the chart board then reflects it as if this estimate was known at the beginning of the sprint. What we would like to see if a spike in the chart. The time estimate should be applied based on the date that the issue was created.

This is important in having a true representation of the burndown. It's valuable to see how the burndown is affected by new tasks arising mid-sprint.

The only known workaround for us is to enter an original estimate of "1 minute", and then set the appropriate "remaining estimate" as the actual time estimate. But this isn't intuitive...