Repository navigation
Description
Tip
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
Is your feature request related to a problem? Please describe.
Attendees get an update email for too many kinds of edits to an event. For example, fixing a typo in the description, changing the end time, changing the recurrence or adding another attendee can all send a new email to everyone, which is noise. Only important changes should send an update.
Describe the solution you'd like
Send an update email when:
- the start changes (
DTSTART, orDUEfor tasks) - an occurrence is skipped (
EXDATE) - the location changes (
LOCATION) - the event is cancelled
Do not send an update email when:
- the title or description changes
- the end date changes (
DTEND,DURATION) - the recurrence changes (
RRULE,RDATE) - the attendee list changes, for attendees who were already invited. Newly invited attendees still get an invitation and removed attendees still get a cancellation.
Technically this is the list of significant change properties in TipBroker
(apps/dav/lib/CalDAV/TipBroker.php:27), which currently contains
DTSTART, DTEND, DURATION, DUE, RRULE, RDATE, EXDATE, STATUS, SUMMARY, DESCRIPTION, LOCATION.
It should become DTSTART, DUE, EXDATE, LOCATION. The change is local to Nextcloud, no sabre patch needed.
When an email is sent, its contents stay the same and can still list all changes.
Describe alternatives you've considered
- Using sabre's default list (RFC 5546,
3rdparty/sabre/vobject/lib/ITip/Broker.php:69). It still emails on end date and recurrence changes, so it does not meet the requirements. - Emailing when the event goes from tentative to confirmed. That would be useful, but the invitation email does not show the event status today, so attendees would not know the event was tentative.
STATUSstays out of the list until the invitation shows it. This is a follow-up.
Additional context
How the current logic works:
- A message is significant if the attendee's
forceSendisREQUEST, the set of instances the attendee is part of changed, or the md5 hash of the listed properties changed (TipBroker.php:406-410, hash built inBroker.php:957-982). IMipPlugin.php:105skips the email when the message is not significant.- Cancellations use a separate path (
STATUS:CANCELLED), so they are not affected by the list. ATTENDEEis not part of the hash, so adding or removing attendees already does not email existing attendees. This needs a test.- Someone newly added to an instance of a recurring event still gets an invitation (existing "set of instances changed" rule,
TipBroker.php:408-409). - The diff shown in the email uses a separate list (
IMipService.php:50), which stays unchanged.
Acceptance criteria:
- Changing
DTSTART,DUE,EXDATEorLOCATIONsends an update email. - Changing the title,
DESCRIPTION,DTEND,DURATION,RRULEorRDATEalone does not send an email. - Adding or removing an attendee does not email existing attendees. New attendees still get the invitation, removed ones the cancellation.
- A newly invited attendee, or a newly added instance, still gets an invitation.
- Cancelling an event still sends a cancellation.
- Unit tests in
apps/dav/tests/unit/CalDAV/TipBrokerTest.phpcover each kept and each dropped property. - Release note, since the email behaviour changes for users.
Follow-up (separate ticket): show the tentative state in the invitation email, then notify on tentative to confirmed.
Assisted by Claude Code:claude-sonnet-5-5
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fields📄 To do
- StatusShow more project fieldsTriaged
Activity
SebastianKrupinski commentedon Nov 17, 2026
We should keep the following
STATUS - This is changed when a event is cancelled or made tentative
SUMMARY - This is debatable, as its only the title of the event, but if the organizer updated the title I think it should be sent
DESCRIPTION - This should be sent, if a organizer updates required information in the description, additional links for instance it should be sent
These should also be sent, if organizer shortens or adjusts an event the participants need to be updated
AndyScherzinger commentedon Nov 17, 2026
@SebastianKrupinski we did decided in the planning to change it as described. I get your view that it makes sense to keep some as is, but user feedback actually shows that we should change it because people do not want it.
So let's please have it changed accordingly. Should people than change their minds again we can still reconsider, but for now, it shall be changed.
SebastianKrupinski commentedon Nov 17, 2026
Hey @AndyScherzinger
Nope problem, I can make the changes.
But FYI... I think the users feed back might have been due to a bug that caused emails for any change to be sent out...
#64317
It was only released in the last NC maintenance versions. This should reduce the amount of emails significantly...
AndyScherzinger commentedon Nov 17, 2026
Hi @SebastianKrupinski
understood and a good point, yet generally speaking the planning round agreed that the mails should be further cut down and looked at would is seen as information not worth informing about.
SebastianKrupinski commentedon Nov 17, 2026
I understand and I am not fighting the change but I think this is going to cause more confusion and problems for our users then the current situation... especially for external attendees because we also send an updated ics file that updates external attendees calendar event in the same email (the emails are not needed for internal users as the events get updated directly).
For instance:
Not sending an update on end date changes (DTEND, DURATION), organizers regularly make mistakes and adjust the length of a event, imagine the organizer, accidentally creating the event for 1 hour then changing it to 2 hours, external attendees would no longer get an update.
Not sending an update on RRULE, RDATE changes, same scenario as above, any change in frequency or occurrences would be missed... also this will cause duplicate events when using "Update this and future" as using this function we first update the existing event "RRULE" with a truncation and then create a new series.
I think we should consider some alternatives:
since internal user events already get updated using iTip (directly modified in the database) there is no need to updated users using iMip (email sending), so we cloud skip sending emails for most changes, other then create and cancel. But still send them to external attendees.
we can send the updates as machine readable scheduling updates only, they have no user readable text, and are processed by most external clients directly without user interaction.
add a "do you want to notify every one" option when saving changes, just like "gmail" does for instance.