nextcloud / nextcloud/calendar
[Bug]: Recurring calendar events get ignored in free/busy display when trying to schedule a new event
Open
@SebastianKrupinski is already working on this.
Since Feb 19, 2025.
1. to develop
bug
Feature: Scheduling
hotspot: recurring events
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
⚠️ 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
- Subscribe to a CalDAV calendar
- Create a new event on your main calendar
- Get to the "Choose time" dialog
- 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
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.
Assessment
This issue has not been assessed yet.