Marking a recurring task as complete on thunderbird will not reflect to iOS reminders.
Categories
(Calendar :: Tasks, defect)
Tracking
(Not tracked)
People
(Reporter: aaszym, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36
Steps to reproduce:
(Both TB and Reminders signed in to Radicale CalDav server)
- Create a daily repeating task on iOS reminders.
- Mark the task as complete for the day on TB.
Actual results:
The task is marked as complete for the day on TB, but not iOS reminders.
Expected results:
The task should also be marked complete on iOS reminders for the day.
Comment 1•9 months ago
|
||
Recurring tasks in Thunderbird seem to sync incorrectly with at least the two I tested -- Apple Reminders and KDE KOrganizer.
This seems to reproduce the issue consistently (in my case, using a Baikal CalDAV server -- so it's not unique to Radicale either):
In Thunderbird:
- Create a task due on September 1 and set it to repeat daily.
- Mark the September 1 task complete; it creates a new one for September 2
- Mark the September 2 task complete; it creates a new one for September 3
At this stage, everything looks correct in Thunderbird...but after syncing, if you look in Apple Reminders (tested on both iOS and MacOS):
- The original September 1 task is showing incomplete and overdue (incorrect)
- The September 2 task is not visible anywhere (even in the completed task list) (incorrect)
- The September 3 task is not visible anywhere (incorrect)
And if you look in KOrganizer:
- The original September 1 task is duplicated; one copy shows incomplete (incorrect) and the other shows completed (correct)
- The September 2 task is shown completed (correct)
- The September 3 task is not visible anywhere (incorrect)
Feels like there's some significant difference in how Thunderbird handles recurring tasks vs. these other tools.
Comment 2•9 months ago
|
||
I created two [seemingly] identical tasks -- one using Thunderbird and one using Apple Reminders. Then I marked the first one in each series "complete" to see what happened.
In Thunderbird, marking the original task complete resulted in the ICS data on the server containing two "VTODO" segments...the first with the original event still with the original due date and NOT marked complete, and then a second with the same UID, same due date, but marked complete. They both also contain "X-MOZ-GENERATION:1".
In Apple Reminders, the original task with its UID has the due date changed to the new date (i.e., next recurrence) and a NEW task with a NEW UID is created with the previous date, no recurrence, and marked complete. In other words, it doesn't actually mark an instance of the recurring event complete, it creates a "fake" past event and marks it complete and changes the due date of the original task to its next iteration.
It looks like Reminders doesn't know how to handle the "multiple VTODOs with same UID" method that Thunderbird is using...it just reads the first one, which is a recurring task with the original due date that is not marked as completed.
Description
•