Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-50067

Previous events and repeat end date of a series lost after editing a recurrence

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      When editing a single item within an event series (created before the update) all previous events are removed after the edit!!!

            [CONFSERVER-50067] Previous events and repeat end date of a series lost after editing a recurrence

            DavidA added a comment -

            Hi Thomas,

            I've just tested with a new event (type "Event") and the combo box where the event type was originally chosen is disabled. Can you tell me in which view (my calendars or in pages, etc) you could change the event type of existing events?

            The combo box is actually one of the problem with the current event edit popup - for instance, it doesn't make much sense to change an event type from non-JIRA types to JIRA types. Of course, we could hide the JIRA options for existing events, but we felt that we could tackle the complexity of the popup as a whole.

            The event edit popup is also very complex. It allows the user to perform one of the below;

            • Change a single event
            • Change an event series
            • Change a single occurrence of an event series

            And at the same time, move the event to a different calendar. If the event type combo box was enabled, it will also need to allow the user to move it to a different calendar as a different type.

            My gut feeling is that we may require more specific UI to communicate all those intents, but that's where we need feedback about.

            In regards to how we migrate all events created before Team Calendars 4.0 to event type "Event" is because we couldn't assume legacy types map to specific event types for all users. For instance, a people calendar in another organisation may not be leave, birthdays or travel at all - it might actually be some sort of a roster calendar. So we thought it was best to migrate it as a more generic type (Event).

            DavidA added a comment - Hi Thomas, I've just tested with a new event (type "Event") and the combo box where the event type was originally chosen is disabled. Can you tell me in which view (my calendars or in pages, etc) you could change the event type of existing events? The combo box is actually one of the problem with the current event edit popup - for instance, it doesn't make much sense to change an event type from non-JIRA types to JIRA types. Of course, we could hide the JIRA options for existing events, but we felt that we could tackle the complexity of the popup as a whole. The event edit popup is also very complex. It allows the user to perform one of the below; Change a single event Change an event series Change a single occurrence of an event series And at the same time, move the event to a different calendar. If the event type combo box was enabled, it will also need to allow the user to move it to a different calendar as a different type. My gut feeling is that we may require more specific UI to communicate all those intents, but that's where we need feedback about. In regards to how we migrate all events created before Team Calendars 4.0 to event type "Event" is because we couldn't assume legacy types map to specific event types for all users. For instance, a people calendar in another organisation may not be leave, birthdays or travel at all - it might actually be some sort of a roster calendar. So we thought it was best to migrate it as a more generic type (Event).

            Thomas Krause added a comment - - edited

            ?? it's a combo box - that's what it is. And it's enabled for events created after the migration.

            You made all events from before the migration an event type 'event'. These events are in fact leaves, travels, birthdays etc. that's the simple reason why one would like change the event type. too exotic?

            Thomas Krause added a comment - - edited ?? it's a combo box - that's what it is. And it's enabled for events created after the migration. You made all events from before the migration an event type 'event'. These events are in fact leaves, travels, birthdays etc. that's the simple reason why one would like change the event type. too exotic?

            DavidA added a comment -

            Hi Thomas,

            We deliberately disabled changing event types because we feel that we don't have a good UI for it at the moment.

            We thought we'd release 4.0 to get some feedback from customers such as yourself in regards to how changing the event type is useful, so we can come up with a good UI for it.
            I've raised TEAMCAL-1654 to track this requirement. Would you mind to provide us some feedback why you need changing event types?

            DavidA added a comment - Hi Thomas, We deliberately disabled changing event types because we feel that we don't have a good UI for it at the moment. We thought we'd release 4.0 to get some feedback from customers such as yourself in regards to how changing the event type is useful, so we can come up with a good UI for it. I've raised TEAMCAL-1654 to track this requirement. Would you mind to provide us some feedback why you need changing event types?

            The repeating events edit seems to work again. Thx.

            Different topic: What I see is that when going from 3.2.6 to 4.0.0 I couldn't change the event type of existing events. I assume you have reasons to restrict that (migrated events..), I thought we have to live with it although it's tedious to recreate a lot of entries with the right event type. Now going from 4.0.0 to 4.0.1 I can't change the event type of entries generated with 4.0.0 as well. This becomes weird now. I don't think this is acceptable going forward.

            Thomas Krause added a comment - The repeating events edit seems to work again. Thx. Different topic: What I see is that when going from 3.2.6 to 4.0.0 I couldn't change the event type of existing events. I assume you have reasons to restrict that (migrated events..), I thought we have to live with it although it's tedious to recreate a lot of entries with the right event type. Now going from 4.0.0 to 4.0.1 I can't change the event type of entries generated with 4.0.0 as well. This becomes weird now. I don't think this is acceptable going forward.

            DavidA added a comment -

            4.0.1 can be downloaded from the marketplace now.

            DavidA added a comment - 4.0.1 can be downloaded from the marketplace now.

            DavidA added a comment -

            Hi Thomas,

            I've just released 4.0.1. The edit behaviour now should be similar to 3.2.x. Please let us know if you notice any problems.

            DavidA added a comment - Hi Thomas, I've just released 4.0.1. The edit behaviour now should be similar to 3.2.x. Please let us know if you notice any problems.

            DavidA added a comment -

            Thanks for the detailed information, Thomas. I confirm there's a problem with how repeating events are processed at the moment. I'll take a look at this as a high priority issue - I'll see if I can get a fix out soon.

            DavidA added a comment - Thanks for the detailed information, Thomas. I confirm there's a problem with how repeating events are processed at the moment. I'll take a look at this as a high priority issue - I'll see if I can get a fix out soon.

            Ok, it also happens for newly created periodic events. And more funny things happen. A series that was setup to end on a certain date was changed to 'repeat never' without user interaction. Furthermore the beginning of the series was changed from an earlier start date to the edited event (later in time).

            Seeing all that I would rate team calendars 4.0 as unusable.

            Thomas Krause added a comment - Ok, it also happens for newly created periodic events. And more funny things happen. A series that was setup to end on a certain date was changed to 'repeat never' without user interaction. Furthermore the beginning of the series was changed from an earlier start date to the edited event (later in time). Seeing all that I would rate team calendars 4.0 as unusable.

            Yes, periodic events, setup with a previous version of team calendars. editing one item in this series worked with team calendard 3.2.6 (and before) and is broken with the 4.0 update where previous event are deleted on an edit.

            Thomas Krause added a comment - Yes, periodic events, setup with a previous version of team calendars. editing one item in this series worked with team calendard 3.2.6 (and before) and is broken with the 4.0 update where previous event are deleted on an edit.

            DavidA added a comment -

            Maybe I misunderstood your problem description - I thought you edited a single instance of a repeating event, and then finding the previous repeat occurrences gone. Is that the problem? Otherwise, would you mind providing the problem reproduction steps?

            DavidA added a comment - Maybe I misunderstood your problem description - I thought you edited a single instance of a repeating event, and then finding the previous repeat occurrences gone. Is that the problem? Otherwise, would you mind providing the problem reproduction steps?

              dchui DavidA
              b1fcecca8615 Thomas Krause
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: