Welcome to the Jazz Community Forum
Burndown chart does not show correct start date
hi,
We are using RTC V4.0.6.
While using burndown charts, we are seeing issue, where the start date of sprint is shown as previous day.
Burndown chart is showing data starting from 27-Sep-2015, where as sprint start date is only 28-Sep-2015.
(Not able to upload , since it requires reputation > 60).
Also the ideal burndown line stop at 100hrs mark (of y axis) and does not show the ideal burndown upto zero hours.
Accepted answer
Seeing the screenshot from the escalation. here is my finding:
The screenshot shows me the burdown is actually starting from the 28. The x-axis starts from the beginning of the 28th (midnight), the next tick is the end of the 28th. The actual Burndown dot falls inside the 28th. The x-axis is time scaled. So when we say the 28th. that is not a single dot. It is actually a date/time range.
The screenshot shows me the burdown is actually starting from the 28. The x-axis starts from the beginning of the 28th (midnight), the next tick is the end of the 28th. The actual Burndown dot falls inside the 28th. The x-axis is time scaled. So when we say the 28th. that is not a single dot. It is actually a date/time range.
One other answer
The Burdown x-axis is time scaled and not date scaled. And given that the ETLs run once a day at a time chosen by the users, there will always be a + or - 24 hour imprecision. But I do not see why this is an issue. We tend to get complaints about the end date of the sprint where users want it to be extended by 24 hours to give the users the chance to close or reassign work right after the sprint finishes. I do not see how having the trend start from 24 hours before the sprint actually starts, would make the report less useful. I would argue it is actually a good thing as it could show you information related to the sprint before the sprint actually started.