You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using caldav integration with Infomaniak ksuite calendar, the event created by cal.com does not contain the appropriate timezone. This lead to an invitation email sent from Infomanial to all attendees with confusing informations.
Steps to Reproduce
Setup caldav integration with infomaniak
Set a team event
Book a event
Wait for invitation email sent from Infomaniak
Actual Results
The invitation email shows time in GMT +00:00
Expected Results
The invitation email shows time in GMT +01:00 (The organizer and attendees timezone)
Technical details
Evidence
This is the notification email sent by cal.com. It shows the correct timezone, but the ics file attached does not contain any timezone information.
This is the invitation email sent by Infomaniak. The body shows 13:30 GMT +00:00, which is confusing for all attendees.
This is the warning message I get when editing the event in the infomaniak calendar.
Please note that the time zone used to create the event (UTC) is different from that of your current browser (Europe/Paris)
The text was updated successfully, but these errors were encountered:
Issue Summary
When using caldav integration with Infomaniak ksuite calendar, the event created by cal.com does not contain the appropriate timezone. This lead to an invitation email sent from Infomanial to all attendees with confusing informations.
Steps to Reproduce
Actual Results
Expected Results
Technical details
Evidence
This is the notification email sent by cal.com. It shows the correct timezone, but the ics file attached does not contain any timezone information.
This is the invitation email sent by Infomaniak. The body shows 13:30 GMT +00:00, which is confusing for all attendees.
This is the warning message I get when editing the event in the infomaniak calendar.
The text was updated successfully, but these errors were encountered: