Summary

      Users are unable to save their changes to a Single Occurrence of a Repeating Event they've edited within Team Calendars. The page refreshes and the change is reverted back to its original configuration. This only appears to affect Events which are repeating; single, non-repeating events can be edited.

      Environment

      • Confluence Server 6.4.1
      • Team Calendars 5.5.4

      Steps to Reproduce

      1. On a Team Calendar, Create an event which has a repeat
      2. Save Event
      3. Edit one of the Events (either change it's title, date/time, Who, etc); ensure "Edit this instance only" is checked
      4. Save Changes to event

      Expected Results

      The Single Event is updated with the new information

      Actual Results

      Calendar refreshes and change does not exist:
      Confluence Logs:

      2018-04-05 17:59:03,066 WARN [http-nio-8090-exec-15] [extra.calendar3.util.TimeZoneUtil] tryParseDateTimeStringForEventEdit Unable to parse date null
       -- referer: https://localhost:8090/display/~XXXX.XXXX/calendars | url: /rest/calendar-services/1.0/calendar/events.json | traceId: 7a550765b4b9cc40 | userName: XXXX.XXX
      
      java.lang.NullPointerException
      	at com.atlassian.confluence.extra.calendar3.rest.statemachine.statehandlers.UpdateRescheduleEventStateHandler.onState(UpdateRescheduleEventStateHandler.java:41)
      	at com.atlassian.confluence.extra.calendar3.rest.statemachine.statehandlers.UpdateRescheduleEventStateHandler.onState(UpdateRescheduleEventStateHandler.java:16)
      	at com.atlassian.confluence.extra.calendar3.rest.statemachine.EventUpdateStateMachine.triggerOnState(EventUpdateStateMachine.java:111)
      

      Resolution

      Upgrade to Team Calendars version 6.0.12 or above, which contains a fix for this issue.

      Some customers report the issue persists even after upgrading to the fixed version (such as 6.0.17). Please watch this ticket to receive the latest updates.

      Notes

      Appears to be related to: CONFCLOUD-55639

      Workaround

      1. Delete the Individual Calendar Event that needs to be Edited and create a new Event with the intended changes.
      2. Exporting the .ical and import it back to Confluence did the trick

        1. 1. create event daily.jpg
          1. create event daily.jpg
          93 kB
        2. 2. edit one Entry.jpg
          2. edit one Entry.jpg
          60 kB
        3. 2018-04-23 19_36_18-Team Calendars - TEST SERVER.png
          2018-04-23 19_36_18-Team Calendars - TEST SERVER.png
          155 kB
        4. 3. add name.jpg
          3. add name.jpg
          83 kB
        5. 4. second event same day.jpg
          4. second event same day.jpg
          63 kB
        6. 5. second user.jpg
          5. second user.jpg
          55 kB
        7. full_error.txt
          35 kB

          Form Name

            [CONFSERVER-55287] Unable to Edit Single Event Instance in Repeating Events

            We are seeing this bug in Confluence 6.15.1 and Team Calendars 6.0.27.

            David Stallard added a comment - We are seeing this bug in Confluence 6.15.1 and Team Calendars 6.0.27.

            Updated calendar to 6.0.20 and no more lengthy errors

            We're on CONF 6.8.0 and Team Calendars 6.0.20 and are not having any more issues...
            Thanks for the update and fix !!!

            Merle Fischer added a comment - Updated calendar to 6.0.20 and no more lengthy errors We're on CONF 6.8.0 and Team Calendars 6.0.20 and are not having any more issues... Thanks for the update and fix !!!

            Same trouble:

            • Confluence: 6.8.5
            • Team Calendars: 6.0.17

             

            Igor Myagchev added a comment - Same trouble: Confluence: 6.8.5 Team Calendars: 6.0.17  

            We are also getting a lengthy error when trying to save the change to the individual event.

            Michelle Vincent added a comment - We are also getting a lengthy error when trying to save the change to the individual event.

            Merle Fischer added a comment - - edited

            @Rudy Slaiby, thanks for the update!
            @Amanda Fernandez Anusuyia, it's friday after all

            happy weekend to you both.

            Merle Fischer added a comment - - edited @Rudy Slaiby, thanks for the update! @Amanda Fernandez Anusuyia, it's friday after all happy weekend to you both.

            christof.koenig & m.fischer1 that was my mistake. I updated the fixed version instead of the affected version. Sorry for the troubles. I have also updated the workaround that might be helpful while the bug is fixed. - Cheers!

            AmandaFernandez (Inactive) added a comment - christof.koenig & m.fischer1 that was my mistake. I updated the fixed version instead of the affected version. Sorry for the troubles. I have also updated the workaround that might be helpful while the bug is fixed. - Cheers!

            christof.koenig and m.fischer1 We acknowledge that this issue is not yet resolved. We are actively working on this. In the meantime, the recent change to the fixVersion was mistakenly applied to the fixVersion rather than the affectedVersion.

            Rudy Slaiby added a comment - christof.koenig and m.fischer1 We acknowledge that this issue is not yet resolved. We are actively working on this. In the meantime, the recent change to the fixVersion was mistakenly applied to the fixVersion rather than the affectedVersion .

            @Christof König, you are not alone. We are also still batteling with this bug though supposedly we're on the fix-version "TV-6.0.17"... I think that's why they added this lovely sentence to the resolution description above:
            "Some customers report the issue persists even after upgrading to the fixed version (such as 6.0.17). Please watch this ticket to receive the latest updates."
            it does make me laugh a little when the most recent update to this ticket is that 6.0.17 is added to the fixed versions, plus another workaround.. dios mios - happy friday.

            Merle Fischer added a comment - @Christof König, you are not alone. We are also still batteling with this bug though supposedly we're on the fix-version "TV-6.0.17"... I think that's why they added this lovely sentence to the resolution description above: "Some customers report the issue persists even after upgrading to the fixed version (such as 6.0.17). Please watch this ticket to receive the latest updates." it does make me laugh a little when the most recent update to this ticket is that 6.0.17 is added to the fixed versions, plus another workaround.. dios mios - happy friday.

            @Amanda Fernandez Anusuyia

            TC-6.0.17 does not fix the issue, we still have to use the Workaround (export-import)

             

            Christof König added a comment - @Amanda Fernandez Anusuyia TC-6.0.17 does not fix the issue, we still have to use the Workaround (export-import)  

            I tried 6.10.1 but still the error exists

            Christof König added a comment - I tried 6.10.1 but still the error exists

              dluong Duy Truong Luong
              mgomez@atlassian.com Manny
              Affected customers:
              16 This affects my team
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: