Burndown report including today - where there is no data
4 answers
Is this 1.0.1.1, 2.0M3D1?
In 1.0.1.1, the Burndown report had an overflow issue. This has been fixed in 2.0.
We recently moved to 1.0.1.1. Are you saying that until 2.0 is released and we move to that that we have to live with the erroneous burndown report?
As this is a production server we aren't using pre-release versions of RTC.
I understand your concern. Can you please raise a work item and I will attach a version of the Burndown report that only shows the historical data (no data from today)? If that is not acceptable, I will discuss with our management team and see how we can provide a patch for yourserver. You are the third person complaining this.