[Bug]: Set then remove working hours result as always BUSY-UNAVAILABLE
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
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
Adding then removing availability times in settings/user/availability, then removing all the slots lead to be always unavailable in free/busy calendar, with FREEBUSY;FBTYPE=BUSY-UNAVAILABLE:20251122T000000Z/20251122T170000Z
Before adding availability, all the time was free.
Steps to reproduce
With an all-new user account (test1) :
- Go to mync.tld/settings/user/availability
- Set availability and save
- Delete all the availability slots and save
- Go to the calendar, add an event, check the free/busy
- OR with another user : in the top-right Contact menu, search for "test1" and look the availability of this user.
Expected behavior
Remove all time slots should reverse to initial state (all free).
Maybe get a button for set "all free" or "never free" ?
Nextcloud Server version
31
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
Nginx
Database engine version
None
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
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.
Research direction
No source file or test is named. Start by reproducing the availability sequence in settings/user/availability, then trace how empty slots are used when generating calendar free/busy data. Done means removing every slot restores the initial all-free result instead of BUSY-UNAVAILABLE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100