Open AndrewRTsao opened 9 months ago
I checked main
today, it works correctly.
First day - Monday
First day - Sunday
Timestamps are 7 days apart.
@egor-ryashin So I can confirm that the issue is still reproducible on main
(it's likely a corner case). See screenshots - tested on both v0.38.2
and main
.
Steps to reproduce:
Rill-311-Ops
example projectAmerica/Chicago
and first_day_of_week
to SunMedian Time to Resolve Ticket (Hours)
from main dashboard viewOct 29 - Nov 30
and make sure that metric trends is set to week
Describe the bug There are issues with proper DST handling in the pivot table when opening the time detail dimension view and DST is included as part of the filtered time range. This issue will be further exacerbated if
first_day_of_week
is configured and set to a different value (e.g. Sunday), resulting in erroneous weekly columns on the wrong days to be displayed along with incorrect calculations. Originally reported by a customer here. We may want to extend the solution covered in #3494 (notion doc) to also apply to time detail dimension views as well.To Reproduce Steps to reproduce the behavior:
first_day_of_week: 7
property to the dashboard YAMLExpected behavior The pivot table should display the correct weekly columns, both data and the date / day shown in the column header, regardless if UTC or a different timezone with DST is being used.
Actual Behavior The pivot table displays incorrect weekly columns when a non-UTC timezone is being used where DST is a consideration.
Screenshots
DST issue with EST and no
first_day_of_week
set:No DST issue when using UTC with no
first_day_of_week
set:DST issue with CST and
first_day_of_week: 7
set:No DST issue with UTC and
first_day_of_week: 7
set: