I use a calendar that is synced via owncloud's CalDAV interface over several computers that are partly equipped with KOrganizer and partly with Thunderbird/Lightning. Whenever I change a recurring event in Lightning by shifting the start and/or end time, the whole recurring event disappears in KOrganizer's calendar view. Reproducible: Always Steps to Reproduce: 1. Create a recurring event on a CalDAV calendar 2. Use another application (e.g. Thunderbird Lightning) to add an exception (in my case different start and/or end times) to the event. 3. Wait until the CalDAV calendar has been synced back to KOrganizer Actual Results: The exception makes the whole event series disappear in the KOrganizer calendar. The exception is present and labelled correctly as exception in akonadiconsole. Expected Results: KOrganizer should display the recurring event and the changed exception correctly.
Created attachment 84031 [details] Raw payload of exception from akonadiconsole
Confirming this issue. Zimbra, korganizer-4.14.4-6.fc21. Having exception in recurring event (weekly meeting) causes means the whole series is gone.
I wasn't able to reproduce this with KOrganizer 5.19.3, but my mix of software is different from the original report. Can you still reproduce the bug? What I did: - I used mailbox.org as the CalDAV provider. - I used the web interface, to avoid any problem with Thunderbird. - I created a recurring event, and waited for it to sync down to KOrganizer. - I made one occurrence an exception, and waited for it to sync. The change synced properly, and no events disappeared.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I couldn't reproduce it either on 5.19.3. Looks like it has been fixed.