1707032 - Recurring tasks via CalDAV do not maintain their 'completed' status

Status: RESOLVED INVALID

(Calendar :: General, defect)

Description

[Michael von Glasow]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

1. Set up calendar and tasks with a CalDav server and an old Thunderbird version (up to ca. December 2020).
2. Set up a recurring task.
3. Whenever an instance of the recurring task becomes due, mark it as completed.
4. Repeat this for a few instances.
5. Upgrade to Thunderbird 78.7.1.
6. Examine the list of tasks.

Actual results:

Previous instances of the recurring tasks (which had already been marked as completed before the update) now reappear and show as incomplete. If I manually set them to Completed, the status will be reset upon sync.

Expected results:

Completion status (as previously set) is honored and the tasks no longer show as open.

Comment 1

[Thomas D. (:thomas8)]

Michael, can you add a screenshot after blacking out private data? Use Attach New File button above comment 0.

Comment 2

[Michael von Glasow]

OS is Ubuntu 20.04, with Thunderbird from the OS package repositories. The server is running DAViCal.

I just ran a few extra tests:

• Recurring tasks in local storage (create a weekly task, starting a few weeks in the past and ending a few weeks into the future, then mark some of the past instances as complete)
• Same on the CalDAV calendar, sync after marking a few past instances complete
• Repeat the CalDAV tests with variations: complete the second instance but leave the first one uncompleted; complete the third instance, sync, then complete the second one
• Non-recurring task on CalDAV

Results:

• Non-recurring tasks are not affected; I can mark the task completed and it will keep its status.
• Recurring tasks in local storage are also not affected; completed instances will keep their status.
• Instances of recurring tasks on CalDAV can be marked completed but will lose their status upon synchronization. Exception: one instance maintains its completion status.
• The instance to maintain its completion status is the first one that got marked complete (i.e. based on the time the completion flag got set, not based on start date).

This bug began showing with an update deployed sometime between January–March 2021, though I failed to record the exact version numbers.

I also have an Android app accessing the same DAViCal instance, where the completed instance have not been reset.

In conclusion, the issue seems to occur when reading tasks from a CalDAV server (tasks on the server are not altered). The first instance which got set to Completed retains its completion status, whereas the flag is ignored for all later ones.

Comment 3

[Michael von Glasow]

Attachment: Screenshot at 2021-04-22 20-47-39.png

Comment 4

[Martin Schröder [:mschroeder]]

This should be fixed since Thunderbird 78.8.0... most recent version is Thunderbird 78.10.0. I hate to say, but OS package repositories are not helpful if you have to wait more than 2 months for bugfix releases.

Comment 5

[Michael von Glasow]

Thanks, then the issue is that OS package repos are slow to pick up the fix. I have filed a bug for Ubuntu.

Comment 6

[Thomas D. (:thomas8)]

(In reply to Martin Schröder [:mschroeder] from comment #4)

This should be fixed since Thunderbird 78.8.0... most recent version is Thunderbird 78.10.0.

Martin, would you know which bug should have fixed this?

I hate to say, but OS package repositories are not helpful if you have to wait more than 2 months for bugfix releases.

Michael, could you try if you experience the same problem if you use the current Linux version of TB downloaded directly from www.thunderbird.net? As Martin pointed out, Linux distros/packages are often trouble causers.

(In reply to Michael von Glasow from comment #5)

Thanks, then the issue is that OS package repos are slow to pick up the fix. I have filed a bug for Ubuntu.

Thanks. So let's close this for now based on Martin's comment 4.