Here's something exciting. One of our servers is set to Denver time. Some of our Customers are on the East Coast.
They run reports, using rollup on days and months. Their Time Zone is set for EST (since, well, they're on EST).
So. When they set up their report to do a Monthly Max or Delta, and run it in Denver (SERVER TIME), it runs swell. When they run a report using their own local timezone (EST, in this case) the rollup appears to run the report on the MST (SERVER timezone) settings.
This causes confusion, since the "monthly" reports are actually last day or previous month to day before the last day of this month, due to the 2-hour timeshift, and the midnight hour.
Here's what we see:
Our reports (running on a user with EST Time Zone)
has this line:
"TS_Start - 2020/07/31 22:00:00 MDT to 2020/08/31 22:00:00 MDT"
when set for "monthly" rollups.
Their TimeZone is set to EST, but the reports adjust to MDT to run the report.
If we set their Timezone to Mountain (or server time zone) the following line comes out:
"TS_Start - 2020/08/01 00:00:00 MDT to 2020/09/01 00:00:00 MDT"
Which is what I expect to see. Notice in the previous line, the start and end are 7/31 to 8/31, when we really want 8/1 to 9/1.
I guess what I expect to see, when a report is ran by a user with EST Time Zone Settings, would be this:
"TS_Start - 2020/08/01 00:00:00 EST to 2020/09/01 00:00:00 EST"
Which bit of obviousness am I missing here?