-
Notifications
You must be signed in to change notification settings - Fork 24
The interview scheduled time is displayed in UTC in calender invitation and in SCHEDULE INTERVIEW page #597
Comments
@sdgun this happens for the customer user, right? Customer user sees time in UTC. |
@maxceem This happens for the JC who schedules the interview using the 'Select Interview Time' link from "Schedule your interview for ..." email which comes after customer submits the interview request |
@sdgun Got it. This email is sent by Google Calendar, so it must be using the timezone which is set inside the google calendar JC Google Account. Could you please check it out? |
@maxceem This JC user has IST set as the primary TZ |
Hmm, @sdgun and what about the Customer's user calendar? As this event is initially created inside Customer's Google calendar, maybe Google uses the Customer's Calendar timezone. |
@maxceem I checked the customer's calender too, it also has IST as the primary TZ. Did you notice in the attached video in this issue description, the interview time displayed before submitting is changing to UTC time after submitting? Not sure why the time is changing after submitting. |
Ah, sorry, I've missed that. Hmm, strange... |
@sdgun the time which is shown on the thank you page is fixed: Regarding the time which is shown inside the Google Calendar email. As per my testing it always uses timezone which is used inside the JC's Google Calendar settings for me. For example, I've changed JC's Google Calendar Timezone to Marocco GMT+1, and I've got Google Calendar Email in Marocco GMT+1 time, though in all other places I use different timezone. |
This issue is fixed now. 2021-12-28_11-34-19.mp4 |
Steps
Schedule an interview from a customer
Confirm a time and set up interview from JC through the email link
After JC submits the interview scheduling, the time displayed on the screen is changing to UTC and even in the calender invitation the time is sent in utc
2021-12-23_11-28-08.mp4
The text was updated successfully, but these errors were encountered: