Calendar and Timezone Issue #calendar #timezone


John Russell
 

Hi All,

My groups has been using ZOOM to schedule video meetings for some weeks, so I was very excited to see that I could now schedule a ZOOM meeting and set reminders using the Groups.io Calendar. But when I started to do this, I noticed that our timezone is still set to CET (UTC+1) for Austria. The clocks have gone forward and we now have CEST which is UTC+2 as our current timezone.

Does Groups.io update the timezones to Summer Time or Daylight Savings Time automatically?  Do I have to do that manually now? I have not scheduled the ZOOM meeting as I do not want to confuse my members by starting a ZOOM meeting at the wrong time. Using ZOOM is already quite tricky for some of them.

I don't even see CEST as an option in the Default User Settings (Admin -> Settings -> Default Sub Settings). Is this a bug that I should report in beta?

Regards
John Russell
Austria


Duane
 

On Sat, Apr 11, 2020 at 05:25 AM, John Russell wrote:
Does Groups.io update the timezones to Summer Time or Daylight Savings Time automatically?  Do I have to do that manually now?
You shouldn't need to change anything.  I'd do a test event (and not invite the group) to verify.  After you create the event, hover over it on the calendar to see what time it's scheduled.  Hopefully it will show local time with UTC+2 below that.  Because different locations change the clocks (or not) on different dates, the TZ shown is for 'normal' time and should adjust what's displayed on the appropriate date.  If it doesn't, that would need to be reported as a bug.

Duane
--
GMF's Unofficial Wiki: https://groups.io/g/GroupManagersForum/wiki
Official Help: https://groups.io/helpcenter


John Russell
 

Hi Duane,

By the time I started to create a test event today, the timezone has changed to CEST (UTC+2) and it looks like all the timezones have been changed to times like BST (UTC+1) for London and all the US times are EDT, CDT etc. I know that quite a few changes have been made to the ZOOM integration as a result of various issues reported by Andy Wedge in Beta and this may have resulted in this timexzone issue being solved. as well.

Regards
John Russell
Austria