Fix Timezone hell in OnCall Schedule (and calendar) #496

Open
opened 2026-04-05 16:20:04 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @GunniBusch on 4/27/2025

TL;DR
Handoff time in In OnCall schedule will force its timezone to the calendar widget; problematic with daylight saving, since if the selected date is in the winter time period, in the summer the calendar shows the event one hour wrong.

So basically if you have selected a date for the hand-off time, it will force its daylight saving timezone to every Calendar entry. This means, if it lies in winter, you will see that in the summer your calendar shows your on-call roaster starts earlier, but you will still be on-call following your actual time.

This means 2 things,

  1. hand-off time is a time not a date time (hand-off time not hand-off date time).
  2. don’t use hand-off time

Interesting is number 2, since why ditch this? Because it is utterly useless and complicates things. Just use a start date time, and then an interval, how often it should switch between users.
Hand-off time influences only the first roaster from my experience and from my Quick Look over the the schedule related classes in the source code.

I am not sure if your custom date time class will allow this, but let’s see.

This is just something a normal user would not care about but in my opinion this is not just a useless feature, but actually a really annoying bug

*Originally created by @GunniBusch on 4/27/2025* TL;DR Handoff time in In OnCall schedule will force its timezone to the calendar widget; problematic with daylight saving, since if the selected date is in the winter time period, in the summer the calendar shows the event one hour wrong. So basically if you have selected a date for the hand-off time, it will force its daylight saving timezone to every Calendar entry. This means, if it lies in winter, you will see that in the summer your calendar shows your on-call roaster starts earlier, but you will still be on-call following your actual time. This means 2 things, 1. hand-off time is a time not a date time (hand-off **time** not hand-off date time). 2. don’t use hand-off time Interesting is number 2, since why ditch this? Because it is utterly useless and complicates things. Just use a start date time, and then an interval, how often it should switch between users. Hand-off time influences only the first roaster from my experience and from my Quick Look over the the schedule related classes in the source code. I am not sure if your custom date time class will allow this, but let’s see. This is just something a normal user would not care about but in my opinion this is not just a useless feature, but actually a really annoying bug
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#496