We have experienced an unexpected behaviour of the Date types of fields:
* When a person sitting e.g. in Singapore sets up the publishing date or approval date in CMP for 10 June, it will show up as 9 June for users in Europe
* We understand this might be due to time zone difference that when it turns to 10 June in Singapore, it´s still 9 June in Europe
* We understand this might be helpful for the Time type of fields – so it when the publishing time is set to 12:00 in Singapore, it´s shown as 6:00 AM in Europe – so it´s the same moment in time
* However, this might cause issues with the dates – when a colleague in Singapore sets a publishing date to 10 June, another colleague in Europe will see it 9 June and will publish a day earlier.
* This is an issue in particular in the multiregional teams where colleagues in different timezones collaborate on delivering a Task (e.g. Social posts.
* Here we would expect the date to be the same or all time zones and reflect the timezones only in the Time fields. In other words, the Dates should be the same all around the world
EXAMPLE USE CASE:
* Lucy is a MarComms manager based in Hong Kong and requests the global Social Media team to publish a LinkedIn post 1 July (Date field at since the post is time critical, Lucy mentions in "Additional info" in the Task Brief it should go out 10 AM BST.
* Social Media team based in Europe (CEST receives the request and see the publishing date in the Brief as 30 June (as CMP reflects the time difference
* Social Media team schedules the post for 30 June 10 AM
* The post goes out a day earlier than Lucy requested which caused issues as the post should have been posted at the exact date and time.