nextcloud / nextcloud/calendar

Events of meeting proposal have an accept/decline/maybe button

Open
#8,834 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop design: brainstorming 🧠 enhancement Feature: Scheduling
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. User A create a meeting proposal
  2. User B opens calendar
  3. User B clicks on one of the proposed events
  4. User B Clicks on "Accept", "Decline", "Tentative"
Expected behavior

Not sure, I think the following would work:

  • do not show the buttons at all
    • maybe show link to proposal voting view (as send by link through mail)
  • show the buttons, but clicking them open the proposal voting view
    • maybe preselects vote for what the user voted
Actual behavior

User sees "Accept", "Decline", "Tentative" but clicking the buttons has now effect.

Image
Calendar app version

6.6.0

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

None

Database engine version

None

PHP engine version

None

Nextcloud version

No response

Updated from an older installed version or fresh install

None

List of activated apps

Nextcloud configuration

Web server error log

Log file

Browser log

Additional info

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 issue in the Calendar app by creating a meeting proposal, opening a proposed event, and clicking Accept, Decline, or Tentative. Trace the event action handling and proposal voting view, then confirm the expected behavior with maintainers before changing it; done when these controls no longer appear ineffective and the chosen behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.