nextcloud / nextcloud/calendar

No attendee response email sent when responding via link

Open
#7,356 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs info
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce
  1. Make sure to enable "Send invitations to attendees" in /settings/admin/groupware
  2. Create a calendar event and invite Person A.
  3. Person A gets an invite email.
  4. Let Person A click on "Accept" or "Decline".
  5. See how you as the inviting person don't get a response email.
Expected behavior

You should get an email about the response of the invited person. Same thing for changes in attendance that the invited person might make later.

Actual behavior

Response emails are just sent when the invited person is responding via a CalDAV client like Apple Calendar or the Nextcloud web interface - but not if they respond through the links in the invitation email.

Calendar app version

5.2.2

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

Start at the invitation email response links and compare their Accept or Decline handling with the CalDAV and Nextcloud web-interface response paths. Verify that the inviting person receives response emails for initial responses and later attendance changes made through the links.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.