Project: jirasoftware
Issue GHS-5069: Figure out what to do with issues which come into a sprint with no statistic value and then change half way through
- Put all items in to the data table at the bottom (i.e when they're added or removed from the Sprint) even if they do not have an estimate and therefore don't affect the burndown Add issue to sprint with no estimate, then change estimate, only shows as statistic value change in table. This problem is particularly bad when you then later remove the issue from the sprint - as the issue addition and removal is completely hidden from the table and is not shown as scope change.
Story points: 8