Working with Time Zones

Overview - Local Times Define All Times

Dates in Clarizen Go are based on the local time of the user who set them.

This is reflected wherever you are in Clarizen Go, for example, in the Activity section of the Task. 

Example

Carlos works in the UTC + 0 time zone, and creates a Task at 8 am. Alisha works in the UTC -10 time zone, so for her, the Task is created at 10 pm on the previous day.

mceclip0.png

Start and Due Dates

Start and due dates refer to the beginning and end of the day, respectively. From a time perspective, the day starts at midnight and ends a minute before midnight.

Example

Carlos works in the UTC + 0 time zone, and sets a due date for January 2nd. This really means the due date is January 2nd at midnight. For Alisha in the UTC -10 time zone, the due date is January 1st, since the time is converted in the background to 2 pm on the previous day.

Sprints

Sprints are defined to begin on a specific date for a predefined period. As described above, the start and due dates are set based on the time zone of the user who created and defined the sprint. On the time level, the sprint becomes active at midnight on the start date, and ends just before midnight of the due date.

Example

A sprint will begin and end at the same time for all users regardless of the local time zone. If Carlos, our Scrum Master is in the UTC +0 time zone, and sets up a sprint to begin on Monday. For Alisha in the UTC -10 time zone, the Sprint will become active on Sunday evening, at the same point in time, but earlier on the calendar. 

Sprint Charts

Sprint charts always show data based on the local time of the user (Scrum Master) who defined the Sprint. Unlike Task dates and Sprint start/end times, which users see as different times according to their time zone, users in all time zones see the same charts. 

Example

If Carlos in the UTC +0 time zone set up a sprint to begin on Monday, for Alisha in the UTC -10 time zone, the latest (current) day in the Burndown chart is Monday (based on Carlos’s time zone), while for Alisha it’s still Sunday.

Milestones

The Milestone date is based on the time zone of the user who created the Milestone. Therefore, the Milestone will arrive at different times (and even dates), depending on the time zone for each user.

Notifications

Notifications are also sent based on the local time zone of the entity’s owner. Therefore all users will get notifications at the same time, but reflected in Clarizen Go in their local time zones.

Sync with Clarizen One

Local dates and times in Clarizen Go are sent to Clarizen One in the UTC time zone, and then converted into the date/time of the organization in Clarizen One.

Start and due dates are handled differently in Clarizen Go and Clarizen One:

  • In Clarizen Go the start date is set to midnight, for example, May 1 means May 1 at 00:00. The due date is set to a minute before midnight, for example, May 1 means May 1 at 23:59.
  • In Clarizen One, dates and times are based on the organization’s defined working days and hours, by default Monday to Friday, 08:00 to 16:00. So the start date for May 1 means May 1 at 08:00 and the due date for May 1 is May 1 at 16:00.

 

Have more questions? Submit a request

Comments