Burndown chart starts from "floor"
Hi all,
We're using Burndown report for current iteration in our project. It's quite useful, but sometimes starting day of iteration is a day of planning. For example, we create new iteration today, make it current one and set today as starting date. Then we plan some work items for this iteration. Next day the chart is starting from zero(which is expected behaviour) and it becomes not so worthy. Th reason is that report uses data collected the night before the day displayed (default setting).
1) If we setup 23-55 as a snapshot time for collecting data, other "warehouse" reports may become broken or incorrect (as well as some of our custom BIRT reports).
2) If we set tomorrow as iteration starting date, then planning and all stuff like load bars, progress bars etc will be incorrect.
Any other ideas?
We're using Burndown report for current iteration in our project. It's quite useful, but sometimes starting day of iteration is a day of planning. For example, we create new iteration today, make it current one and set today as starting date. Then we plan some work items for this iteration. Next day the chart is starting from zero(which is expected behaviour) and it becomes not so worthy. Th reason is that report uses data collected the night before the day displayed (default setting).
1) If we setup 23-55 as a snapshot time for collecting data, other "warehouse" reports may become broken or incorrect (as well as some of our custom BIRT reports).
2) If we set tomorrow as iteration starting date, then planning and all stuff like load bars, progress bars etc will be incorrect.
Any other ideas?