Timezone Refactoring

Document created by John_Streeter on Dec 18, 2015Last modified by JohnStreeter on Dec 8, 2017
Version 2Show Document
  • View in full screen mode

Hello, we have heard your feedback regarding time and date handling in our product and are excited to announce that we are simplifying and improving how we handle timezones. The timezone changes affect how users see and interact with time and dates in the product to ensure the data displayed is relevant and consistent.


Previously our product had three ways of managing timezone settings which caused misconfiguration or misunderstood configurations that often resulted in confusing behavior for users. The product allowed the workspace to set a timezone, the user to set a timezone and also inferred the user’s operating system timezone. Different methods would be used at different times causing inconsistency, as well as multiple methods would be used at the same time causing conflicts and incorrect data.


The new functionality will remove the option for a user to set their timezone in their profile settings. Users will see time in the product based on their system setting and time will always be displayed relevant to their current timezone. The Admin will still set the workspace timezone and this data will be used to store all times in that workspace on the backend. Users will not see the workspace timezone and will have no impact on it. Please see attached file for more details.