-
Notifications
You must be signed in to change notification settings - Fork 64
Description
Hello,
Recently I started to investigate the way the recurrent tasks are being displayed in the scheduler on the day of the DST change and there is one situation which I believe is working incorrectly.
For the timezone "Europe/Warsaw" I have created two recurrent tasks starting on 22nd Oct 2023 and ending on 22nd Nov 2023. One tasks starts at 12am and finishes at 3am and the other one starts at 12am and finishes at 2am. In Warsaw on the 29th of Oct there is a change from Summer to Winter time (3am -> 2am) and this is a day I found unexpected behaviour. I will refer to two tasks created on this specific day as "Task 12-2am" and "Task 12-3am"
In the database the Task 12-3am has following details:
{
startDatetime: "2023-10-28T22:00:00Z"
endDatetime: "2023-10-29T01:00:00Z
duration: 180 // value in minutes
}
And the Tasks 12-2am is defined as:
{
startDatetime: "2023-10-28T22:00:00Z"
endDatetime: "2023-10-29T00:00:00Z
duration: 120 // value in minutes
}
While creating dataSource
for the scheduler I used both the strings in the format given directly from the databse (i.e. values in UTC as well as after converting them to the local timezone using method
moment.tz(datetime_from_database, "Europe/Warsaw" ).format()
Where datetime_from_database
where simply the startDatetime or endDatetime of the specific task.
For both values the result has been the same.
The results can be seen on image below.
Everything works as expected for the Task 12-2am. However the task 12-3am for some reason is being displayed as if it would have 1h duration.. The expected behaviour would be to display it as identical to Task 12-2am since we are moving 3am -> 2am on the 29th Oct.
I am attaching a screenshot with identical situation created for Google Calendar.
Thank you in advance for checking this out.