Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-60520

Recurring events from Outlook causes 1 hour difference in Team Calendar due to daylight savings

XMLWordPrintable

      Issue Summary

      When you subscribe to an Outlook calendar via URL in Team Calendar, recurring events created during European daylight savings will not show the correct timings once daylight saving ends.

      Steps to Reproduce

      1. Set your Outlook and TC calendars to be on GMT+1 timezone (or any European timezone affected by daylight savings).
      2. Create a recurring event in Outlook calendar during summer 2020 (e.g. July 2020).
      3. Set the recurring event monthly or weekly at 2:30pm.
      4. Generate the iCal URL to subscribe to the calendar.
      5. In Confluence, open up your calendars and click on ...Subscribe by URL.
      6. Input the URL generated in Outlook earlier.
      7. Check the recurring event you created in step #2 and compare the difference in timing between events in July 2020 and November 2020.

      Expected Results

      All events should be set to 2:30pm.

      Actual Results

      The event in July is set to 2:30pm, but after daylight savings ended in late Oct, all recurring events after that are set to 1:30pm.

      Notes

      1. If you download the ICS file for the Outlook calendar and import it to Confluence (... > Import Calendar), the issue isn't seen. All recurring events are set to the expected timing (in this case, 2:30pm).
      2. If you subscribe to the Outlook calendar in Google calendar, the timing appears correctly as what you see in Outlook. Only Confluence has the 1-hour difference in timing.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              aknight@atlassian.com Alex K
              azolkefli Athirah Zolkefli (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: