Availability report with service time showing incorrect information

I just noticed this forum post from May 5th where this problem in 1.6.0.p11 is confirmed as a bug: