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
At some point, we decided not to show the timezone when displaying time. Times are shown based on the user's local time, which is detected through the browser. For example, if a user schedules a time for the next day at 9 AM, it will be displayed in their local time. If another user views the schedule, the time will adjust to their timezone, such as 9 AM ET for one user and 6 AM PT for another.
This approach seems to create some confusion. Should we add a disclaimer, caption, or tooltip to inform users that the displayed time is based on their location? More discussion needed here
The text was updated successfully, but these errors were encountered:
The place where we tripped over this in the Census send was in the 7-day chart on the dashboard. Some messages sent in the evening EST, but showed as happening on the following day, presumably because the chart is in UTC.
Were you aware of any other timezone glitches, @CathyBeil ?
@ecayer Interesting... I'm making a note here to check how the daily stats are counted.
If messages are sent evening EST and they show up the next day because of UTC, are we okay with that? Confusion arises between UTC and local time primarily because they represent time differently
At some point, we decided not to show the timezone when displaying time. Times are shown based on the user's local time, which is detected through the browser. For example, if a user schedules a time for the next day at 9 AM, it will be displayed in their local time. If another user views the schedule, the time will adjust to their timezone, such as 9 AM ET for one user and 6 AM PT for another.
This approach seems to create some confusion. Should we add a disclaimer, caption, or tooltip to inform users that the displayed time is based on their location? More discussion needed here
The text was updated successfully, but these errors were encountered: