Skip to content

fix(dav): mark declined room booking as declined in the room calendar - #66573

Open
lazerg wants to merge 2 commits into
nextcloud:masterfrom
lazerg:fix/issue-66568-declined-room-booking
Open

lazerg wants to merge 2 commits into
nextcloud:masterfrom
lazerg:fix/issue-66568-declined-room-booking

Conversation

@lazerg

@lazerg lazerg commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Summary

When a room or resource is already booked, the auto-reply declines the new invite, but the copy that parent::scheduleLocalDelivery() already stored in the room's calendar stays NEEDS-ACTION and opaque. That copy keeps the slot busy in free/busy and makes isAvailableAtTime() decline later bookings even after the original one is deleted. The stored copy is now updated to PARTSTAT=DECLINED for the room and TRANSP:TRANSPARENT, so it no longer counts as busy. I checked it against the steps from the issue with calendar_resource_management: after deleting event A the room shows free and a new booking for the slot is accepted.

Checklist

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: lazerg <lazerg2@gmail.com>
Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: lazerg <lazerg2@gmail.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Declined room/resource booking stays in the room's calendar as NEEDS-ACTION and blocks free/busy

1 participant