Go give it a thumbs up and hopefully it’ll be addressed in the Timezones release which it’s currently tagged for.
@flamber I added a Sample Dataset reproduction to that issue but it didn’t seem to work for you guys, but I think my screenshots show that it’s happening in my setup. Looking forward to the timezones release as this issue is really turning some of my key users off.
@notrom Are you still seeing this (even with Sample Dataset) on 0.33.6? I'm on master right now, which has some more timezone fixes, but I cannot reproduce. Can you post your Diagnostic Info from Admin > Troubleshooting, since it contains some timezone info.
I changed my report timezone to match yours, @notrom, (Pacific/Auckland) and the same scenario looks correct to me on master, so this will likely be fixed for you in 0.34. One difference I'm noting is that the SQL now includes with timezone:
yeah, I think you’re right @notrom. I did some tests grouping by month an I still get the previous one. It doesn’t look like a TZ issue from what I can gather. I’ll add another reproduction to that github issue.
@maz is there a jar file for the master branch? I’d be more than happy to test this but don’t have a suitable environment here to build it myself at this time.
We’re aiming to do a release candidate build by the end of the week, so that would probably be a good time to try it out. You can watch this page: https://github.com/metabase/metabase/releases