Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.15.0
-
None
-
8.15
-
2
-
Severity 3 - Minor
-
Description
Issue Summary
When accessing Jira issue datetime fields through the Jira icalendar plugin (Confluence Team Calendar integration) Reproduced on Jira 8.8.0 and 8.13.2 with icalendar plugin 1.8.2
Steps to Reproduce
- Create Jira and Confluence instance with Server time as CDT (Chicago)
- Set your User time in both instances to New York
- Create custom fields with datetime type data
- Set the dates for the following, and access these events in Jira Team Calendars: some dates return incorrectly in the response from Jira - see changes from Jira Icalendar plugin version 1.8.0 to 1.8.2:
14th March 2020:
1.32 AM -> 1.32 AM
3.32 AM -> 3.31 AM
4.32 AM -> 4.32 AM
5.32 AM -> 4.32 AM
15th March 2020:
1.14 AM -> 12.14 AM
2.32 AM -> 1.32 AM
3.14 AM -> 3.14 AM
4.14 AM -> 4.14 AM
Expected Results
The times returned from the icalendar plugin would be the same as previously.
Actual Results
The times are off by 1 hour between 5AM 14th March and 2AM 15th March, in the day where the Daylight savings change happens.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- relates to
-
CONFSERVER-60281 Team Calendar showing wrong start time after daylight savings goes into effect and out of effect
- Closed