nextcloud / nextcloud/calendar
Shared cancelled event does not propagate to attendees
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Create a calendar C by user U1
- Share calendar C with users U2 and U3 in sharing options
- (as user U2) Create event E in calendar C, inviting user U3
- (as user U2) Delete/cancel event E in calendar C
- (as user U3) Observe as the event E is NOT deleted/not marked as cancelled in personal calendar of user U3.
Expected behavior
Event E is deleted from both calendar C and personal calendar of U3 (or deleted from calendar C and marked as cancelled in personal calendar of U3)
Actual behavior
Event E is only deleted from calendar C
Calendar app version
5.3.2
CalDAV-clients used
Thunderbird/Nextcloud UI
Browser
Firefox
Web server
Apache
Database engine version
PostgreSQL
Nextcloud version
Nextcloud Hub 9 (30.0.10)
Updated from an older installed version or fresh install
Updated from an older version
Additional info
Interestingly, updates to event times ARE indeed pushed down to the personal calendar of user U3. It's only the deletes that are not pushed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the shared-calendar cancellation flow with U1, U2, and U3 using the Nextcloud UI or Thunderbird, then inspect the CalDAV sharing and event-deletion path. Compare deletion propagation with the event-time update behavior described in the issue. Done means cancelling an event created in a shared calendar removes it or marks it cancelled in the attendee's personal calendar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100