nextcloud / nextcloud/calendar

Out-of-Office planing in the calender or allow multiple out-of-office settings in parallel

Open
#6,931 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage enhancement
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Is your feature request related to a problem? Please describe.

Not sure if this belongs to the calendar or rather to the server, please move the ticket if needed.

The problem I'm trying to solve: I use the Nextcloud calendar heavily, also the appointment booking feature. I can only set one out-of-office in the "availability"-settings, so if more vacations days are already planed I need to remember to set them after each other. But it could still happen that people use the appointment feature booking a appointment before I could set the out-of-office to my next vacation.

I solve it at the moment by adding my vacations manually to the calendar but this leads to double entries as soon as the out-of-office is set.

Describe the solution you'd like

Two ideas I have in mind:

  1. Probably the easy solution: Let the user configure multiple out-of-office times in the availability-settings so that I can add there all my vacation / out-of-office times as soon as I know them. They should then also be automatically removed if the date has passed.

  2. Detect vacations in the calendar and set from their the out-of-office automatically when the vacation starts and disable it when the vacation ends. The out-of-office text could be copied from the description of the calendar event. Other things like "replacement" might be tricky. Another complicated part might be to distinguish "vacation / out-of-office" times from other calendar entries. Maybe this could be solved with a dedicated caldav property (out-of-office)? The benefit would be that I would just need to keep my calendar up-to-date and the rest would happen "magically" in the background

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names only the availability settings, calendar events, and appointment-booking feature; no files, tests, or entry points are provided. Start by locating those areas and deciding whether multiple configured periods or calendar-driven status is in scope. Done should define behavior for overlapping, expired, and automatically applied out-of-office periods.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.