Timeslots show differnece than the time scale on the day light saving start and end day

[Ramy Selim]

There is an issue in angular schedule component on the day light saving start and end day, the event slot is moved by one hour from the timescale how can I fix this

[Ashokkumar Karuppasamy]

Hi Ramy,

Your reported problem “Timeslots show differnece than the time scale on the day light saving start and end day” is considered as a bug. The fix for this defect will be included in our upcoming weekly patch release, which is expected to be rolled out by first week of April, 2024. You can track the status of the fix at the following link:

Feedback : https://www.syncfusion.com/feedback/51873/timeslots-show-differnece-than-the-time-scale-on-the-day-light-saving-start-and

Regards,
Ashok

[Indhumathy Loganathan]

Hi Ramy,

Sorry for the inconvenience.

Currently, we are working to resolve your reported issue with priority. However, we need some additional time. The fix will be included in our patch release scheduled on first week of May 2024. We appreciate your patience.

Regards,

Indhumathy L

[Indhumathy Loganathan]

Hi Ramy,

The fix for the issue “Timeslots show difference than the time scale on the day light saving start and end day” has been included in our weekly release version 25.1.41. Upgrade to the latest version to resolve the issue.

 

Sample: https://stackblitz.com/edit/ej2-angular-schedule-dst-issue-sample-latest-version

However, the additional issues mentioned in Scheduler will be included in 14th May 2024 release as promised. Please track the feedback for fix status.

Regards,

Indhumathy L

[Indhumathy Loganathan]

Hi Ramy,

We deeply regret the inconvenience.

The provided fix is introducing the other DST falling timezone. So it will take some additional time to provide a common solution for all DST and non-DST timezones. We will include the fix in our May 21, 2024 patch release. We appreciate your patience.

Regards,

Indhumathy L

[Indhumathy Loganathan]

Hi Ramy,

Sorry for the inconvenience.

The fix requires changes in our base, so we need additional time to provide the fix without introducing any other breaking. Currently, we are working on this and will include it in the May 28, 2024, patch release.

Regards,

Indhumathy L

[Indhumathy Loganathan]

Hi Ramy,

As explained in our previous update, the fix requires major changes, and we were facing more complexity at our end. Since it requires more time than expected, it may be moved to June 11, 2024.

Regards,

Indhumathy L

[Ashokkumar Karuppasamy]

Hi Ramy,

Thank you for your update. We have fixed the mentioned issue in the upcoming weekly patch release. In the meantime, you can find the custom package containing the fix in the shared package.

please get back to us if you need any further assistance.

Regards,

Ashok

Attachment: ej2schedule_1_4c135640.zip

[Swathi Ravi]

Hi Ramy,

 

The fix for the issue “Timeslots show differnece than the time scale on the day light saving start and end day” has been included in our weekly release 26.1.38. Upgrade to the latest version to resolve the issue.

 

Release notes:  Essential Studio for Angular Weekly Release Release Notes (syncfusion.com)

Sample: Schedule-dst-EET (forked) - StackBlitz

Root Cause: The time has been calculated from the new Date(). So the DST date doesn't convert the proper time cells.

 

Regards,

Swathi Ravi

[enrica.carpena]

Hello, has this issue also been fixed for React Scheduler? My team are dealing with the same issue for UK and US timezone.

[Ravikumar Venkatesan]

Hi enrica.carpena,

Sample: https://stackblitz.com/edit/ej2-react-schedule-dst-sample?file=index.js

Thank you for reaching out and bringing this issue to our attention. We understand that your team is experiencing a problem similar to one reported earlier, where event slots are moved by one hour on the start and end days of daylight-saving time.

We want to reassure you that the initial issue reported in the Angular schedule component has been addressed, and we have also implemented a fix for the React Scheduler.

However, to ensure we are addressing your specific scenario, could you please provide more details on the issue? Specifically, it would be helpful to know:

• The exact time zone where you are experiencing this issue.
• The scheduler codes you are using.
• Whether you are setting up time zones for the schedule and appointments.
• Steps to reproduce the issue as you are experiencing it.

We tried reproducing the issue by rendering appointments at 07:50 AM and 07:50 PM in the following time zones, but were unable to replicate it:

• (UTC +01:00) Dublin, Edinburgh, Lisbon, London
• (UTC-08:00) Pacific Time (US & Canada)
• (UTC-07:00) Mountain Time (US & Canada)
• (UTC-06:00) Central Time (US & Canada)
• (UTC-05:00) Eastern Time (US & Canada)

Your input will be invaluable in helping us ensure a comprehensive fix.

Thank you for your cooperation and understanding.

Regards,
Ravikumar Venkatesan

[enrica.carpena]

Hi Ravikumar Venkatesan,

The user's local timezone is set to 

• (UTC +01:00) Dublin, Edinburgh, Lisbon, London

The issue begins at the timeslot 00:00 of March 30, 2025, on the day DST adjusts for UK. This is the sample data showing both start and end time:



In this example, the Schedule is set to America/New_York Timezone. Notice how end time is adding an hour and the event template is not adjusting to the respective time scale. Resulting to messed up schedule times for the rest of the day. This only happens on the 30th of March for UK and March 9 for US, on the days when DST adjust for both regions.

Even without adding a timezone to the Scheduler, the issue always starts on the 00:00 of the 30th of March when system is in (UTC +00:00) Dublin, Edinburgh, Lisbon, London.

Converting the start and end time also ends up with the same outcome.

[enrica.carpena]

Hi Ravikumar Venkatesan,

The user's local timezone is set to 

• (UTC +01:00) Dublin, Edinburgh, Lisbon, London

The issue begins at the timeslot 00:00 of March 30, 2025, on the day DST adjusts for UK. This is the sample data showing both start and end time:



In this example, the Schedule is set to America/New_York Timezone. Notice how end time is adding an hour and the event template is not adjusting to the respective time scale. Resulting to messed up schedule times for the rest of the day. This only happens on the 30th of March for UK and March 9 for US, on the days when DST adjust for both regions.

Even without adding a timezone to the Scheduler, the issue always starts on the 00:00 of the 30th of March when system is in (UTC +00:00) Dublin, Edinburgh, Lisbon, London.

Converting the start and end time also ends up with the same outcome.