1737877 - Allow comments and notes to be added to processed invitations, improve reminder experience.

Status: RESOLVED DUPLICATE of bug 541376

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

Description

[Richard Leger]

+++ This bug was initially created as a clone of Bug #1700110 +++

As per Bug 1700110 Comment 8:

"...

(In reply to Magnus Melin [:mkmelin] from comment #7)

Descriptions and such cannot be editable in invites, but yes the reminder is supposed to I think.

Could Thunderbird allow editing another field if not Description of the invite to allow adding notes/comment?

The iCalendar RFC seems to provide an available field (a VEVENT class COMMENT) that could be used perhaps...

Source: https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.1.4

3.8.1.4. Comment

Property Name: COMMENT

Purpose: This property specifies non-processing information intended
to provide a comment to the calendar user.

Value Type: TEXT

Property Parameters: IANA, non-standard, alternate text
representation, and language property parameters can be specified
on this property.

What I mean is on an invite received...

..."

Comment 1

[Lasana Murray]

Invitations should be treated as read-only because there are conditions where servers may refuse changes or overwrite them.
If you look at Fastmail's troubleshooting guide under "Editing an event doesn't work" you'll see:

You can't edit an event which you didn't create: that is, an event you are invited to.

https://www.fastmail.help/hc/en-us/articles/1500000279841

They still let us to set our X-MOZ properties but I don't think we should rely on that. There can also be situations where the user updates the event on the server (or it is automatically updated) before our local changes resulting in conflicts which is a weird experience for dismissing a reminder.
In the provider re-design, our event meta-data will be stored locally instead of relying on the server. That way we could support notes and reminders better but still should not support editing the main event properties.

Comment 2

[Lasana Murray]

I've updated the title. Let me know if it still captures what your issue is or if I missed something out.