nextcloud / nextcloud/calendar
Allow appointments to conflict check and book a room/resource
Open
Nobody has claimed this yet.
0. to triage
Feature: Appointments
Feature: Rooms and Resources
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Follow up to #1023
- The room/resource should be checked for conflicts when generating slots
- only slots that are also available for the room/resource should be shown
- booking the room/resource should happen at the same time as booking the meeting
- allow suggesting a room/resource by attendees as well as organisers (for group appointments)
- possibly specifying a room and 1 or more resources allowed (ex: appointment is in a Room in Office B, Organiser or Attendee needs Car Resource to get there from Office A. This leads to interesting follow up questions if one of the rooms/resources could be booked for preparation duration + length + follow up duration of an appointment).
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 reading the linked follow-up issue #1023 and tracing the existing appointment slot-generation and meeting-booking flows. Define how room and resource conflicts affect displayed slots, booking atomicity, attendee suggestions, and preparation or follow-up durations. Done means the agreed resource-booking behavior is implemented and covered by the relevant 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