Closed Bug 1676526 Opened 5 years ago Closed 5 years ago

Calendar does not show details for repeating events

Categories

(Calendar :: General, defect)

Product:
Calendar
Component:
General
Version:
Thunderbird 78
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1664731

People

(Reporter: pieter.breugelmans, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0

Steps to reproduce:

  1. Fresh install of Thunderbird 78.4.2
  2. Create a new calendar, from network (CalDAV)
  3. For an existing repeating event scheduled by a colleague, double-click on it.
  4. Click on Edit only this occurrence button

Actual results:

It opens the event in Edit mode, despite the fact that I did not create the repeating event. Instead, I'm an attendee of the event. Only the following fields are populated:

  • Title
  • Start and End times

It does NOT show the event description, attachments nor its attendees.

Expected results:

It should open the event details in read only mode.

This behavior was not seen with this CalDAV calendar when using Thunderbird 68.x. To be clear: I did not perform an upgrade. This behavior is on a a clean install of Thunderbird 78.x.

Upon further testing, it appears to happen when the given event (a single event from the series) has been accepted.

  1. For an existing repeating event scheduled by a colleague to which I did not respond yet, double-click on it.
  2. Click on Edit only this occurrence button
    -> It opens the event details in read only mode as expected
  3. Close the event details
  4. Right click on the event, choose Attendance --> This Occurrence --> Accept --> Do not send a notification
    --> The event color changes to reflect that I have accepted the one for that day.
  5. Double-click on the event
  6. Click on Edit only this occurrence button

Result: It opens the event in Edit mode with the details missing, instead of opening it in read only mode.

Closing this as the issue is resolved. Not sure what went wrong, but removing the calendar and recreating it fixed the issue.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID

This bug was a duplicate of bug 1664731 which could be worked around for existing events by re-creating the affected (cached) CalDAV calendar.

Resolution: INVALID → DUPLICATE
You need to log in before you can comment on or make changes to this bug.