Page MenuHomePhorge

Update our attendee status based on the busyStatus
ClosedPublic

Authored by mollekopf on Jul 28 2023, 1:57 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Feb 20, 1:11 PM
Unknown Object (File)
Mon, Feb 12, 10:57 AM
Unknown Object (File)
Jan 18 2024, 3:43 PM
Unknown Object (File)
Jan 2 2024, 5:22 AM
Unknown Object (File)
Dec 21 2023, 2:43 AM
Unknown Object (File)
Dec 21 2023, 2:15 AM
Unknown Object (File)
Dec 20 2023, 11:33 PM
Unknown Object (File)
Dec 12 2023, 8:00 AM
Subscribers

Details

Summary

It seems, for outlook the busystate is the attendee state.
This means we shouldn't set STATUS based on it, but we should update our
attendee status.

If we are not an attendee, we have to avoid adding an extra attendee
though.

To get consistent behaviour in both directions, we also set the
busyStatus based on the attendee status, which makes sure that we get
the same result no matter if the webclient or outlook is used to set to
tentative or accepted.

Diff Detail

Repository
rS syncroton
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

mollekopf created this revision.
machniak subscribed.

I'm afraid that, if an organizer updates his event, this will add organizer as an extra attendee, looking at update_attendee_status() code.

This revision now requires changes to proceed.Jul 28 2023, 2:16 PM

Another thing is the BusyStatus property spec. does not make sense. https://learn.microsoft.com/en-us/openspecs/exchange_server_protocols/ms-ascal/9a37b42c-6762-4d3e-9e05-9c9221a1cd06 Note that the description is different if it is a part of an Exception.

mollekopf edited the summary of this revision. (Show Details)

Set the attendee status based on busyStatus, and don't set STATUS in ical.

Two notes:

  • I don't know if this actually needs to be outlook specific
  • We ignore this whole conundrum in getEntry, but maybe we should be mapping the users attendee status to busyStatus (I'm not aware of a case where it matters though).

Two notes:

  • I don't know if this actually needs to be outlook specific
  • We ignore this whole conundrum in getEntry, but maybe we should be mapping the users attendee status to busyStatus (I'm not aware of a case where it matters though).

It matters when we set the event status to tentative, which will result in a tenative attendance in outlook, and on the next sync the attendee will be marked as tentative as well.

Do not sync STATUS to the busyStatus

mollekopf edited the summary of this revision. (Show Details)

Also sync the attendee status to the busystatus so we get consistent behaviour no matter if the webclient or outlook is used.

This revision is now accepted and ready to land.Jul 31 2023, 1:21 PM
This revision was automatically updated to reflect the committed changes.