Completing a recurring task incorrectly completes the recurring series instead of advancing it
Categories
(Calendar :: Tasks, defect)
Tracking
(Not tracked)
People
(Reporter: g8796365, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:159.0) Gecko/20100101 Firefox/159.0
Steps to reproduce
Completing a recurring task in Thunderbird does not behave as expected.
Steps to reproduce
- Create a task in Thunderbird Calendar.
- Configure it to recur monthly.
- Open the task list with the filter set to "All".
- Observe that the recurring task is represented by a single entry.
- Mark the recurring task as completed.
- Observe the task list.
- Open the task details.
- Change the task-list filter to "Completed".
- Synchronize the calendar with a CalDAV server and inspect the resulting task in another calendar client.
Actual results
Actual result
The task list displays only one entry representing the recurring task.
Marking it as completed produces no visible change in the task list.
The task details panel reports "Status: Completed on [date]".
No next occurrence appears in the task list.
Switching the filter to "Completed" reveals multiple completed entries, apparently one for each past recurrence date.
The original recurring VTODO is also marked as completed.
After CalDAV synchronization, other clients interpret the recurring task as completed and display it with strikethrough.
The user is therefore left with a completed recurring task rather than an active recurring task with a completed occurrence.
After completing the task, Thunderbird exports the following VTODO:
BEGIN:VTODO
...
STATUS:COMPLETED
PERCENT-COMPLETE:100
...
END:VTODO
The task list displays only one entry representing the recurring task. When I mark this task as completed, its appearance in the task list does not change. The task details panel reports "Status: Completed on ...", however.
Thunderbird also generates completed entries for past recurrence dates, which are visible when the task-list filter is set to "Completed", but not when it is set to "All".
Most importantly, Thunderbird marks the original recurring VTODO as completed while retaining its RRULE. No active next occurrence is displayed.
When the calendar is synchronized through CalDAV, other clients interpret the recurring task as completed and display it with strikethrough.
This makes recurring tasks effectively unusable.
Expected results
Proposed solution: Outlook-style recurring task completion
I propose adopting the approach used by Outlook and also discussed in the original Bug 373775 discussion.
When a recurring task is completed:
- Convert the current task into a normal, non-recurring VTODO.
- Mark this VTODO as completed, preserving its UID, due date, completion timestamp, notes and other properties.
- Create a new VTODO with a new UID.
- Give the new VTODO the original recurrence rule.
- Advance its DTSTART and DUE to the next occurrence.
- Keep the new recurring task active.
This results in two independent tasks:
- A completed historical task representing the occurrence just completed.
- An active recurring task representing the future series.
Advantages
- Completed occurrences are represented as ordinary, independent tasks.
- The active recurring task is never accidentally marked completed.
- Historical tasks retain their completion timestamps and notes.
- Each task has an independent UID.
- No application-specific X-properties are required.
- CalDAV synchronization becomes straightforward.
- Other calendar applications can interpret the completed task and active recurring task independently.
- Addressing the historical objection about overdue occurrences
The discussion in Bug 373775 raised the concern that the Outlook-style approach makes it difficult to handle overdue occurrences completed out of chronological order.
I do not consider this a sufficient reason to reject the approach.
Handling overdue occurrences and advancing the active recurrence are separate concerns.
For example, suppose a monthly task has due dates in June, July and August, and the user completes it in August.
Thunderbird can:
- Create a completed historical task for August.
- Advance the active recurring task to September.
- Optionally create additional completed historical entries for June and July, if that is the desired overdue-task policy.
The number of historical entries created for missed occurrences is a separate product-design decision (and in all honesty, completely irrelevant for most workflows. Most people will just delete the past completed occurrences at some point)
It should not prevent the normal completion workflow from preserving the future recurrence.
The essential requirement is that completing a recurring task must not inadvertently complete the entire recurring series.
Historical context and related bugs
This issue has been discussed for many years:
Bug 373775 – Original problem: completing a recurring task occurrence marks all occurrences completed.
Bug 350174 – Implementation of recurring-task occurrence handling and task-list presentation.
Bug 1872561 – Recurring-task completion problems involving CalDAV.
Bug 1911099 – Interoperability problems involving recurring tasks and Apple Reminders.
The original Bug 373775 discussion also considered the Outlook-style approach of creating a separate completed task and advancing the recurring task.
Bug 350174 subsequently introduced a different task-list design, including safeguards intended to prevent accidental completion of recurring parent tasks.
However, the current behavior still allows the recurring parent to be completed, resulting in the incorrect state described above.
Impact
Recurring tasks are effectively unusable in this situation.
Completing a task should not terminate its future recurrence or cause other calendar applications to interpret the entire series as completed.
This is both a fundamental task-management problem and a CalDAV interoperability problem.
Comment 1•16 days ago
|
||
Independent reproduction of the same signature, Thunderbird 158.0 on Linux (Arch), task on a Synology CalDAV calendar.
A weekly recurring VTODO (RRULE weekly, no due date) was checked off in the Thunderbird UI on separate Thursdays. In the CalDAV store, each completion was written as a COMPLETED override onto the wrong RECURRENCE-ID — always a future occurrence, 2-4 weeks ahead of the actual completion date. Example: the Oct 15 occurrence was marked COMPLETED with a completion timestamp of Sep 21; Oct 22 was completed Sep 24; Oct 29 on Oct 1; Nov 5 on Oct 12. The master VTODO stayed STATUS:NEEDS-ACTION at 0%.
Client-visible effect: the Today Pane hides completed tasks, so the task silently vanishes from the current day until the mis-written future occurrence passes. Server-side inspection (direct CalDAV GET) confirmed the wrong overrides were on the server, so this is written by the client, not a display-cache artifact. Removing the corrupt overrides server-side restored normal behavior; the next UI completion mis-wrote again.
Description
•