Steps to reproduce
      Scenario 1

      1. Login to Confluence
      2. Install Team Calendar
      3. Click on "Calendars" on the top navigation bar
      4. Click on Add Calendar on the top right and add a calendar called "test"
      5. Create a new events called "testing recurring event" and set it to Repeat weekly as per the screenshot below :

        after that click OK
      6. Select on the recurring events and click on Edit as per the screenshot below :
      7. Add admin user to the "Who" field as per the screenshot below :

        then Click OK
      8. click on another recurring event and add test user to the "Who" field as per the screenshot below :

      9. Now go back to the first event that have the admin user added in the "Who" field as per the screenshot below and edit the text to "testing recurring event 2". Please ensure that the "Edit this instance only" is unticked :

      Current result : the first event does not show "testing recurring event 2". It seems that other recurring event is showing the changes but not the event that have user test added to the "Who" field as you can see from the screenshot below :

      Expected result : the first event should show the changes along with all the recurring events.

      Steps to reproduce
      Scenario 2

      1. Login to Confluence
      2. Click on "Calendar" on the top navigation bar
      3. Add a new Calendar named test2
      4. Add event on test2 calendar named "test recurring event" and ensure that Repeat is set to Weekly
      5. Click one of the events to edit and add user "admin" to the "Who" field. Ensuring that "Edit this instance only" is ticked
      6. Click on the same event to edit and add user "test" to the "Who" field. Ensuring that "Edit this instance only" is unticked.

      Current result : the recurring event that we have edited shows that only "admin" is in the "Who" list while others show the changes that was made as per the screenshot below :

      Expected Result : All recurring event should show the changes including one of the recurring event that we have made changes to.

      Scenario 3

      1. Create a recurring weekly event
      2. Edit one specific instance of this recurring event
      3. Add a user on the "Who" field (with "Edit this instance only" enabled)
      4. The following day's event will switch to the same day as the edited event:

        1. recurringEvent1.jpg
          140 kB
          Der Lun
        2. editRecurringEvent.jpg
          110 kB
          Der Lun
        3. editRecurringEvent2.jpg
          142 kB
          Der Lun
        4. editRecurringEvent3.jpg
          86 kB
          Der Lun
        5. editRecurringEvent4.jpg
          111 kB
          Der Lun
        6. editRecurringEvent5.jpg
          117 kB
          Der Lun
        7. editRecurringEvent7.jpg
          116 kB
          Der Lun
        8. changes1.jpg
          113 kB
          Der Lun
        9. recurrentEvent.jpg
          116 kB
          Der Lun
        10. Screen Shot 2020-02-18 at 17.09.42.png
          117 kB
          Felipe Morais
        11. Screen Shot 2020-02-18 at 17.10.14.png
          77 kB
          Felipe Morais
        12. Screen Shot 2020-02-18 at 17.10.37.png
          121 kB
          Felipe Morais
        13. Screen Shot 2020-02-18 at 17.11.01.png
          73 kB
          Felipe Morais
        14. TeamCalendarsTesting.mp4
          4.66 MB
          Ysfin Tazky

            [CONFSERVER-48449] recurring events changes not being reflected correctly

            Alex K added a comment - - edited

            Scenarios 1 & 2 are expected behaviour. Once you "edit this instance only" for any event in a recurring series, that event is separated from the rest of the events in the series. If you then edit another event and select to edit all the events in the series, we have two options, either overwrite all the events with the new data or overwrite all that have not been modified individually. Team Calendars takes the latter approach except for when the user changes the time range for all events. Different calendar clients will handle this differently, for example Apple Calendars does the same as Team Calendars, whereas Google Calendars will take the first approach of overwriting the entire series. It might make sense to have this behaviour be optional, however, that would be a suggestion and not a bug.

            We cannot merge the data as this could lead to conflicts that we cannot reasonably show or handle in the Team Calendars UI.

            Alex K added a comment - - edited Scenarios 1 & 2 are expected behaviour. Once you "edit this instance only" for any event in a recurring series, that event is separated from the rest of the events in the series. If you then edit another event and select to edit all the events in the series, we have two options, either overwrite all the events with the new data or overwrite all that have not been modified individually. Team Calendars takes the latter approach except for when the user changes the time range for all events. Different calendar clients will handle this differently, for example Apple Calendars does the same as Team Calendars, whereas Google Calendars will take the first approach of overwriting the entire series. It might make sense to have this behaviour be optional, however, that would be a suggestion and not a bug. We cannot merge the data as this could lead to conflicts that we cannot reasonably show or handle in the Team Calendars UI.

            Alex K added a comment -

            Scenario 3 is a duplicate of CONFSERVER-57508 and will be fixed in the next release of TC 6.1.0

            Alex K added a comment - Scenario 3 is a duplicate of CONFSERVER-57508 and will be fixed in the next release of TC 6.1.0

            Thomas added a comment -

            Is there any information about when this will be resolved?
            I've noticed that both this issue as well as TEAMCAL-3740 are part of Sprint "Bug Fixing Dec 29". TEAMCAL-3740 was resolved over a month ago, but this issue still seems to be in limbo somehow...

            Thomas added a comment - Is there any information about when this will be resolved? I've noticed that both this issue as well as TEAMCAL-3740 are part of Sprint "Bug Fixing Dec 29". TEAMCAL-3740 was resolved over a month ago, but this issue still seems to be in limbo somehow...

              aknight@atlassian.com Alex K
              dooi Der Lun
              Affected customers:
              8 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: