Dear Maintainer,
* What led up to the situation?
Importing .ics calendar files downloaded from elsewhere, for example
sports schedules
from GoHeels.com, that have DTSTART and DTEND fields demarcated in UTC
with Z at the end to
identify
* What exactly did you do (or not do) that was effective (or
ineffective)?
Importing to an Exchange calendar connected to Evolution results in the
event's time being
set to the UTC time in the local time zone - for example, an event with
DTSTART:20230909T211500Z
DTEND:20230910T001500Z
is imported as starting at 9:15 pm Eastern (my local time zone) and
ending the following
day at 12:15 am Eastern. The correct time would be 5:15 pm - 8:15 pm
Eastern.
Importing the same .ics file to a local calendar via Evolution sets the
time zone as
expected, and importing the same .ics file to the Exchange calendar via
Office 365
(web interface) sets the time zone as expected, so I believe the
problem is with
Evolution's interface with the Exchange calendar.
Thank you for your work!