[Bug]: Recurring calendar events get ignored in free/busy display when trying to schedule a new event

[zilti]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

When trying to schedule a new calendar event, recurring events are not shown as "busy" times in the time selector; meanwhile, one-off events from the same CalDAV calendar do get shown as "busy" blocks.

Steps to reproduce

1. Subscribe to a CalDAV calendar
2. Create a new event on your main calendar
3. Get to the "Choose time" dialog
4. One-off events from the CalDAV calendar will be shown as "busy" time blocks, recurring events however will not.

Expected behavior

Recurring events should be shown as "busy" time blocks as well.

Nextcloud Server version

29

Operating system

Other

PHP engine version

PHP 8.3

Web server

Nginx

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

[SebastianKrupinski]

Hi @zilti

Thank you for the bug report.

Just to clarify you are talking about the the time slots here?

[zilti]

Yes, that's the one 👍

[zilti]

I looked at the .ics file, the two events in question are:

Non-recurring event that gets shown as a "busy" time block correctly:

BEGIN:VEVENT
DTSTART:20250220T104500Z
DTEND:20250220T120000Z
DTSTAMP:20250218T152915Z
UID:4h2irbvbm0lki3gduaotvvdnd5@google.com
ATTENDEE;X-NUM-GUESTS=0:mailto:redacted@redacted.com
SUMMARY:Busy
END:VEVENT

Recurring event that does not get shown:

BEGIN:VEVENT
DTSTART:20250220T130000Z
DTEND:20250220T140000Z
DTSTAMP:20250218T152915Z
UID:3v16vqatk3o02qd9jclt4vv91b_R20250206T130000@google.com
ATTENDEE;X-NUM-GUESTS=0:mailto:redacted@redacted.com
RECURRENCE-ID:20250220T130000Z
SUMMARY:Busy
END:VEVENT

(UIDs have been altered; the timestamp part of the second UID is kept intact.)

[SebastianKrupinski]

Hi @zilti

It did a few quick tests, but you are correct there is a issue. We will add it our list of todo's.