Bug Report T619455
Visible to All Users

Daylight Saving Time is not considered in the exception rule for recurring appointments

created 7 years ago

Hi ,

I am using the scheduler to store recurring appointments for Australia.

One of my recurring appointment is crossing the daylight saving time change date ( 1st April  ).

I am storing the exception rules in UTC time as the appointment in used in multiple time zones.

Now, I am facing an issue, wherein, If I create an exception for 26th March the exception rule is updated as 20180327T090000Z ,
which is correct ( 8 PM AEST to UTC ) and If I create an exception for 2nd April the exception rule is updated as 20180402T100000Z
which is also correct ( 8 PM AEDT to UTC )

However, the schedule is still showing the 2nd April Appointment despite being added in the exception, as it can not identify the Daylight savings.

Can you please check this and let me know how this can be resolved.

Show previous comments (6)

    Hi Maxim ,

    I managed to replicate the issue even in your demo sample for timezone support

    please see below plucker

    https://plnkr.co/edit/CrN0ipyek3WCN6wQQsBI?p=preview

    Step to reproduce :
    Go to calendar day view
    Open any recurring appointment
    delete once occurrence
    Expectation: it should be deleted from the view.
    Issue:
    Instead of deleting it, scheduler appends it to the beginning of the day ( 0800 am ) despite of having the recurrence rule.

    I did it the demo code for devextreme timezone demo as well.

    I am using the exact structure in my code.

    DevExpress Support Team 7 years ago

      Peter,
      The provided description is not quite clear to me. Would you please clarify how it relates to the original issue, exception dates and time shaving in AEDT  time zone? Did you face another issue? Please clarify this. Would you please also record a screencast to illustrate the steps in action? I believe it will make the case clearer.

      DevExpress Support Team 7 years ago

        We reviewed your description again and now the case is clear. Our developers are working on it.

        Answers approved by DevExpress Support

        created 7 years ago

        We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.

        Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.

          Show previous comments (3)
          DevExpress Support Team 7 years ago

            Hello,
            I have updated your plunker sample to use the devextreme@17.2.8-pre-18121 package and now it does not reproduce the issue. I suggest you remove the node_modules directory and the package.lock file. Then, install all packages again and let me know about your results.

              Hi Nikita ,

              I did the investigation and realized that the fix seems to be incorrect.

              Previously, before the fix, the recurrence exception dates were added in the timezone of recurring appointment ( startDate timeZone).
              Now it is been changed and exception dates are added in browser/users timeZone( which is incorrect).

              This leads to existing issue, wherein if the recurring appointment crosses the daylight saving dates, recurrence exception won't work.

              For example,

              if an appointment is starting from 22nd March and daylight have changed on 1st April.
              Recurrence exception won't work.

              I would expect the solution to add the recurrence exception in startDatetimeZone.

              DevExpress Support Team 7 years ago

                Hello Peter,

                I see that the deleted appointment is not shown in the Scheduler now. So, I've created a separate ticket on your behalf regarding this new issue. Please see (T632271: The Scheduler does not save recurrence exceptions in the start date time zone with the hotfix of the T619455 ticket).

                Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

                Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.