Summation Report bug?

Hi Francesca Shiekh,

Would you be able to provide a list of your filters, display summaries, and group by selections that I can replicate the report locally to investigate.

Francesca,

Just taking a quick glance at this, is it possible that there is a GMT offset that is occurring when you run the query via the UI but then that offset is not occurring when you run the query directly in the database?

Kind Regards,

Lori Arce

Thank you Lori Arce, this doesn't explain why the group appears twice in the report

I think Lori Arce's theory is that if you have say +5 hours on your profile then it might be causing your profile to read the date as tomorrow, with the database still thinking it as today. 

Hello.

I can confirm there is something amiss. At first i didn't see it

My GMT offset is +2 . So I created 2 issues let's say on 10/03/2016 both at the same hour mid day. When i run the report from my user they show up good.

Changed one of them to 10/03/2016 close to midnight at 23:45 , ran the report again that case get's moved  to the next day on 11/03 at 01:45 (date_entered + user gmt offset) however these items should stack up with the other items on the same day which they don't ..... the offset one get a different count ... Guess you could mitigate this by doing the summation on a date field instead of a datetime one ?

So looking at your data can make a guess that those 43 cases were possibly made on the 09/03  ?

Hello.

I can confirm there is something amiss. At first i didn't see it

My GMT offset is +2 . So I created 2 issues let's say on 10/03/2016 both at the same hour mid day. When i run the report from my user they show up good.

Changed one of them to 10/03/2016 close to midnight at 23:45 , ran the report again that case get's moved  to the next day on 11/03 at 01:45 (date_entered + user gmt offset) however these items should stack up with the other items on the same day which they don't ..... the offset one get a different count ... Guess you could mitigate this by doing the summation on a date field instead of a datetime one ?

So looking at your data can make a guess that those 43 cases were possibly made on the 09/03  ?

Thank you for the detailed analysis Caim.

I will file a ticket which will hopefully lead to a bug report.

Francesca,

We have an existing defect that may be related to this issue.  Hope this helps.

Lori

Any recommendations on how to deal with some dates getting skipped over to the next day because of the DST (system wide) ?  The date and time from the mysql table is the good one with GMT offset and DST already applied to it ..