Time consistency

[gtolarc]

There is a need for a consistent policy regarding timezone of DateTime.

The DateTime format is internally managed as [fieldName]_utc, [fieldName]_offset, but I think delegating the timezone decision to the browser setting and removing the offset is a convenient way to reduce confusion.

And it would be better to change TextDayTimePicker/DayTimePicker in UI to just express it according to the timezone setting of the browser. How about this?

Timezone representation is a really important area in CMS, and current keystone5 is not clear about this, and there are bugs. I think it needs to be fixed quickly.

[gautamsi]

three is a field DateTimeUtc which does not have offset and it always saves in UTC.

[gtolarc]

I know. However, it doesn't seem intuitive. And it seems to be causing more confusion because there is a problem with the display of the datetime in the current keystone admin frontend.

[ChuckJonas]

The issue simply is the bug with the admin UI. The database should store the time in UTC (as it does). The time should be displayed in the local timezone of the user.

I think the UI component is just broken and selecting a date always overwrites your selection with the previous day.

I created a bug displaying this behavior here:

#6115

[dcousens]

I think we can say this issue has been resolved by #6115, please open a different discussion if necessary

[bladey]

Thanks for the discussion @gtolarcm, @gautamsi and @ChuckJonas, we'll look into this in the near future.