nextcloud / nextcloud/calendar
Overlapping Reservation Conflict Not Detected When Editing Existing Reservation With Resource Of Meeting Rooms
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
1.Reserve room 301 from 2 PM to 4 PM for today.
2.Another user reserves the same room for a different time slot, such as 1 PM to 2 PM.
3.The calendar system successfully creates both reservations without any errors.
4.Second user then decides to edit his reservation to overlap with the first reservation, changing it from 1 PM to 2 PM to 2 PM to 4 PM.
5.The calendar system allows the edit without any warning or error message, even though there is now a conflict between the two reservations (both occupying room 301 from 2 PM to 4 PM).
Expected behavior
The calendar system should prevent the editing of a reservation if it would result in an overlapping conflict with another existing reservation. An appropriate error message should be displayed to inform the user of the conflict before allowing the edit.
Actual behaviour
Currently, the calendar system does not provide any feedback or prevention mechanism for overlapping reservations during edits.
Calendar app version
latest
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
No response
Updated from an older installed version or fresh install
None
List of activated apps
No response
Nextcloud configuration
No response
Web server error log
No response
Log file
No response
Browser log
No response
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 files or tests are identified in the issue. Start by reproducing the reservation edit flow described above and trace where overlapping resource reservations are checked; done means an edit that creates an overlap is rejected with a user-visible conflict message and existing non-overlapping edits still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100