nextcloud / nextcloud/calendar

Option to make appointments not associated with person

Open
#5,519 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage enhancement Feature: Appointments Feature: Rooms and Resources
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.

The current public appointment booking page contains the avatar and name of the owner of the appointment. This is unintuitive if you want to use the booking feature for a room or another resource.

Describe the solution you'd like

'Create Appointmen' modal:

  • add checkbox 'personal appointment' (default: yes)
  • add description 'Your personal avatar and name will be displayed on the appointment booking page.'

Appointment booking page:

  • hide the avatar and 'booking__display-name'
Describe alternatives you've considered

A cooler but a bit more work-intensive alternative would be: If the checkbox 'personal appointment' is unchecked, to show an upload-button for a cusom appointment image and a text input for a custom 'room or resource title' and show these instead of the avatar and the owner's name.

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

Start by locating the Create Appointment modal and the public appointment booking page, then trace how appointment ownership is passed between them. Implement the requested personal-appointment option and verify that an unchecked option hides the owner's avatar and display name; the alternative custom image and title is optional in the issue description.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.