nextcloud / nextcloud/calendar

Some shortcomings when it comes to the new appointment vote feature in calendar

Open
#7,593 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop design 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.

I really like the new appointment vote/proposal feature. However, I've encountered a few shortcomings or design flaws while using it.

  1. I can't select the calendar where the appointment is created after picking one of the proposed dates. It's always my personal calendar. I have to change the appointment by hand afterwards, which is annoying.
  2. If I define a date by holding mouse and dragging it downwards, I get an error for not setting a time after releasing the mouse button. To make it work I have to click one of the timeframes on the left. I think this is a bug.
  3. Showing the free time in the calendar by a crosshatched area is a confusing since usually unavailable timeframes are shown as a solid element in the calendar view. This is the opposite.

But still, great new feature. Keep it up 👍

Describe the solution you'd like

No response

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

Reproduce the appointment vote/proposal flow in the calendar UI, covering selecting a proposed date, dragging to define a date, and the crosshatched free-time display. Start by tracing the frontend entry points for this feature; done means the target calendar can be chosen, dragging does not fail without a separate timeframe click, and availability styling is unambiguous.

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.