Some Team Calendar notifications aren't set with a date parse error

Summary

Team Calendar notifications aren't sent due to a date parse error.

In atlassian-confluence.log this error is thrown, there is no stack trace, just this

2017-08-13 13:04:37,468 WARN [http-nio-8090-exec-4] [extra.calendar3.util.TimeZoneUtil] tryParseDateTimeStringForEventEdit Unable to parse date 
 -- referer: http://confluence.mycompany.com:8090/calendar/mycalendar.action | url: /rest/calendar-services/1.0/calendar/events.json | traceId: cf06ed098f41e2a7 | userName: userXYZ

Environment

• Team Calendar 5.3.19
• SMTP configured

Steps to Reproduce

1. Log in as usera
2. Create an all day event, not repeating
3. Add usera as first invitee (with email address usera@mycompany.com)
4. Add userb as second invitee (with email address userb@mycompany.com)
5. Click Ok

Expected Results

All added users get an email notifying of the event

Actual Results

The below exception is thrown in the atlassian-confluence.log file:

2017-08-13 13:04:37,468 WARN [http-nio-8090-exec-4] [extra.calendar3.util.TimeZoneUtil] tryParseDateTimeStringForEventEdit Unable to parse date 
 -- referer: http://confluence.mycompany.com:8090/calendar/mycalendar.action | url: /rest/calendar-services/1.0/calendar/events.json | traceId: cf06ed098f41e2a7 | userName: userXYZ

The user mentioned in the log does not receive the email, the other users do.

Notes

This seems to be only affecting some users. On testing with 2 users exactly the same, one receives the email and the other doesn't. This is reliable. The error is from this exception

        catch (Exception iae)
        {
            LOG.warn("Unable to parse date " + date + (StringUtils.isNotBlank(time) ? " time " + time : ""));
            LOG.debug("Exception when parsing date:", iae);
            return null;
        }

Based on the error we can see, the date is blank.

Code was introduced with

• TEAMCAL-3764 - refactoring update event logic in CalendarRestResouce to make it more maintianable

However, the bug is likely elsewhere as this code is using date that is sent to it.

Workaround

Add all other users and save the event. Have another user add yourself to the event.