Calendar Tab: recurring Event exceptions cannot be edited by scope #1326

Open
opened 2026-10-07 06:18:15 +00:00 by kayg · 0 comments
Owner

Steps

  1. Connect a writable CalDAV calendar with a recurring Event master that has an EXDATE and a detached RECURRENCE-ID exception.
  2. Open the exception in Calendar and choose Edit Event.
  3. Change the title and submit.

Expected

The User can choose whether to edit this occurrence, this and following occurrences, or the full series. The selected scope saves without changing the other occurrences.

Actual

The edit form offers no scope choice. Submitting the detached exception leaves the Composer open with “Changes could not be saved.” No Event PUT reaches the server. The real Calendar range still expands the COUNT, EXDATE, detached exception, and BYDAY/UNTIL fixture correctly.

Evidence

  • artifacts/bash-calendar/round2-recurrence/exception-edit-failed.png
  • artifacts/bash-calendar/round2-recurrence/recurrence-evidence.txt

Severity: major. This needs a recurrence-scope decision before implementation; no scope behavior was inferred in this bug-bash job.

## Steps 1. Connect a writable CalDAV calendar with a recurring Event master that has an `EXDATE` and a detached `RECURRENCE-ID` exception. 2. Open the exception in Calendar and choose **Edit Event**. 3. Change the title and submit. ## Expected The User can choose whether to edit this occurrence, this and following occurrences, or the full series. The selected scope saves without changing the other occurrences. ## Actual The edit form offers no scope choice. Submitting the detached exception leaves the Composer open with “Changes could not be saved.” No Event PUT reaches the server. The real Calendar range still expands the `COUNT`, `EXDATE`, detached exception, and `BYDAY`/`UNTIL` fixture correctly. ## Evidence - `artifacts/bash-calendar/round2-recurrence/exception-edit-failed.png` - `artifacts/bash-calendar/round2-recurrence/recurrence-evidence.txt` Severity: major. This needs a recurrence-scope decision before implementation; no scope behavior was inferred in this bug-bash job.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal-v0#1326
No description provided.