-
Bug
-
Resolution: Fixed
-
High
-
4.0
-
Confluence 4.3.7
-
Severity 3 - Minor
-
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!!!
- relates to
-
CONFCLOUD-50067 Previous events and repeat end date of a series lost after editing a recurrence
-
- Closed
-
- mentioned in
-
Page No Confluence page found with the given URL.
-
Page No Confluence page found with the given URL.
-
Page No Confluence page found with the given URL.
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
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;
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).