-
Bug
-
Resolution: Done
-
Medium
-
11
-
Severity 2 - Major
-
1
-
NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.
Scenario A:
Profile Time Zone: (GMT+0700)
Team Calendar Event Time: (GMT+0500) 9:00AM - 11:00AM
After import and integration:
Expected result: Google Calendar Event Time: (GMT+0700) 11:00AM - 1:00PM
Actual result: Google Calendar Event Time: (GMT+0700) 9:00AM - 11:00AM
Scenario B:
Profile Time Zone: (GMT+0700)
Team Calendar Event Time: (GMT+0700) 9:00AM - 11:00AM
After import and integration:
Expected result: Google Calendar Event Time: (GMT+0700) 9:00AM - 11:00AM
Actual result: Google Calendar Event Time: (GMT+0700) 9:00AM - 11:00AM
Scenario C:
Profile Time Zone: (GMT+0500)
Team Calendar Event Time: (GMT+0700) 9:00AM - 11:00AM
After import and integration:
Expected result: Google Calendar Event Time: (GMT+0700) 9:00AM - 11:00AM
Actual result: Google Calendar Event Time: (GMT+0700) 7:00AM - 9:00AM
The events time showed in Google Calendar is one hour later compare to what we have in Team Calendar for HongKong (GMT+8) Timezone. Please refer scenario D to reproduce the issue.
Scenario D: Profile Time Zone: (GMT+0800) Beijing, Chongqing, Hong Kong, Urumqi Team Calendar Event Time: Asian/HongKong (GMT+0800) 10:00AM - 11:00AM Expected result: Google Calendar Event Time: (GMT+0800) 10:00AM - 11:00AM Actual result: Google Calendar Event Time: Hong Kong China time zone 11:00AM - 12:00PM
- duplicates
-
CONFCLOUD-48981 Team Calendars and Mac Calendar does not integrate properly (Timezone)
- Closed
- is related to
-
CONFSERVER-48595 Team Calendar is not recording event time correctly for Hong Kong Timezone
- Closed
- relates to
-
CONFCLOUD-72744 Updating timezone does not update Team Calendar's event time
- Closed
-
CONFCLOUD-72765 Integrating Team Calendars using the CalDav integration has the events offset by 1 day
- Closed
- is action for
-
APOLLO-3166 Loading...