Closed Bug 1674059 Opened 6 years ago Closed 5 years ago

Moved CalDAV-calendar entries of a repeating event looses reminder and category information.

Categories

(Calendar :: General, defect)

Thunderbird 78
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1664731

People

(Reporter: sid, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

I moved single entries with the mouse of a repeating event within a WebDAV calendar. This repeating event originally contained a category and also a reminder was set.

Actual results:

The moved events lost the category and also the reminder was disabled. However, all the entries within the original repeating sequence did keep the category and also the reminder was enabled. In order to fix the moved events, I had to edit them manually by setting a category and a reminder. This fixed the issue.

Expected results:

I expect that moved entires out of a repeating event keeps all the information, but only changes the date and the time.

It looks like this is potentially an issue with my WebDAV server, rather then an issue of the Calendar client. I would appreciate if somebody could either confirm or reject this report.

Summary: Moved WebDAV-calendar entries of a repeating event looses reminder and category information. → Moved CalDAV-calendar entries of a repeating event looses reminder and category information.

Correction: I'm using a CalDAV server for calendar synchronization, not a WebDAV.

I verified the behavior of my CalDAV server with some other calendar clients and they did not show this behavior. Thus, I suspect it's an issue in the Lightning Calendar.

This could be a duplicate of bug 1664731 which will be fixed in an 78.x release in the near future.

I'm closing this bug, since with the release of 78.7 in relation of the fix of bug1664731 this behavior was not seen anymore.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.