nextcloud / nextcloud/calendar

participants should be able to suggest a different time after consulting the free/busy information of all other participangs

Open
#3,633 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage
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.
Receiving an invite when you just cannot make means communication must happen to deal with the conflict. This takes time. The email notifications say not to do it via email. The pages behind the links in the notification email provide the option to decline or accept but not "I'd love to accept but can we move this to <select time>"

Describe the solution you'd like
When receiving an invite for a time you cannot make, it would be great to be able to suggest a different time slot. this feature is probably well known from outlook.

Describe alternatives you've considered
Alternative is calling the author of the appointment. Or engaging in a separate email conversation.

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

No files, tests, or entry points are named in the issue. Start by locating the invitation response pages and free/busy handling, then define the expected flow for suggesting an alternative time; done means an invitee can review participants' availability and submit a different slot.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.