We’re aware of the issue, and hope to have a fix ready soon. In the meantime, the workaround is to set the event’s timezone in UTC - it will then be correctly translated to everyone’s local timezone in the UI.
2 Likes