nextcloud / nextcloud/calendar
Minimum time between bookings not respected [appointments]
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 appointment schedule with a set "minimum time before next available slot", such as 2h (planning restrictions section)
- Using the booking link, make and confirm a meeting
- Observe the booking being added to the calendar
- Open the booking link again, observe a slot directly after the first is available, book and confirm it
- Observe two meetings directly after each other have been added to calendar
Expected behavior
If a 2h minimum time between meetings is set, next available slot should be 2h after the previously confirmed one, and it should not be possible to book a earlier slot in case the link was opened simultaneously (after the first is confirmed).
Actual behavior
Currently "minimum time before next available slot" is not respected at all.
Calendar app version
6.2.2
CalDAV-clients used
None, webui
Server operating system
Opensuse Leap
Web server
Apache
Database engine version
MariaDB
PHP engine version
PHP 8.3
Nextcloud version
32.0.8
Updated from an older installed version or fresh install
Updated from an older version
Web server error log
No errors emmited by bug
Other information is added if needed!
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 tracing the booking-link appointment flow described in the reproduction steps, including how availability is calculated after a confirmed meeting and how simultaneous bookings are handled. Confirm the fix by reproducing the two-hour restriction and verifying that an earlier overlapping slot cannot be booked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100