Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.3.20, TC-6.0.25
-
30
-
Severity 3 - Minor
-
12
-
Description
Summary
Team Calendar throw WARNING in atlassian-confluence.log while adding or editing an event:
While adding/editing All Day Event:
2017-12-18 15:53:09,985 WARN [http-nio-8090-exec-2] [extra.calendar3.util.TimeZoneUtil] tryParseDateTimeStringForEventEdit Unable to parse date
-- referer: http://localhost:8090/calendar/mycalendar.action | url: /rest/calendar-services/1.0/calendar/events.json | traceId: ffafa4c5a68de505 | userName: admin
While adding/editing event with time:
2017-12-18 15:53:46,301 WARN [http-nio-8090-exec-6] [extra.calendar3.util.TimeZoneUtil] tryParseDateTimeStringForEventEdit Unable to parse date time 08:00
-- referer: http://localhost:8090/calendar/mycalendar.action | url: /rest/calendar-services/1.0/calendar/events.json | traceId: 3cb2299b6804c2c6 | userName: admin
Environment
Team Calendar 5.3.20
How to Replicate
- Install fresh Confluence 6.5.0 with Team Calendar 5.3.20
- Add an empty calendar
- Set TimeZone to your own local timezone (double check if TimeZone is the same in user profile settings)
- Add a test event
- Check the logs
Expected Results
Team Calendar creates the event with no errors or warning messages (given that the timezone is correct)
Actual Results
The below exception is thrown in the atlassian-confluence.log file:
2017-12-18 15:53:09,985 WARN [http-nio-8090-exec-2] [extra.calendar3.util.TimeZoneUtil] tryParseDateTimeStringForEventEdit Unable to parse date
-- referer: http://localhost:8090/calendar/mycalendar.action | url: /rest/calendar-services/1.0/calendar/events.json | traceId: ffafa4c5a68de505 | userName: admin
Notes
This is the same as CONFSERVER-53188 - Some Team Calendar notifications aren't set with a date parse error. In CONFSERVER-53188, it was found that notifications were not sent were expected as they are not sent to the creator of an event.
Attachments
Issue Links
- is related to
-
-
- Closed
-
- mentioned in
-
Page Loading...