nextcloud / nextcloud/calendar
Resource/room booking conflict handling
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Currently, a booking conflict is not really handled - a resource will decline the booking without the organiser of the conflicting event getting any information about the conflict (who has booked the resource, ...).
Either add a way for the organiser to contact the other organiser and/or possibly give the person that's responsible for the resource priority in all bookings.
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
The issue names no files, tests, or entry points. Start by tracing how resource booking conflicts are declined and how organisers are notified, then clarify whether organiser contact, resource-owner priority, or both is required. Done should be defined by an agreed conflict-handling behavior and corresponding tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100