Duration field with different time zones

[palmen]

I've created a duration field and set the value to 4 hours

If I log in with a user in another timezone and open the same record and check the field it'll display another duration (in this case a user 1 hour ahead of me based on their location).

I've no idea why this is happening and it only happens a few times, most of the time the correct value is shown.

Anyone else who has seen this and can explain why it's happening? It's quiet a big difference in 1h downtime and 0h downtime.

This is what it looks like in the history for the record. Only by opening the record the downtime was changed.

I've had the exact same scenario in another instance as well and struggle to understand why it happends.

[Abhinay Erra]

How was this duration value set? DO you have any script doing this?

[palmen]

The value is set manually, you simply just enter the estimated downtime, in this example 4h for a user in GMT+1 timezone.

When a user in GMT+2 open the record it changes the estimated downtime to 3h.

[Rakesh Mamidi]

How are you setting the value??

in client script, you can use it as g_form.setValue('<duration_field>', '11 01:02:03');

Set a duration field value

[Anurag Tripathi]

I think some other date time field is having an effect on this, that is why with change in timezone this is changing. 4 hour should be 4 hour only in all timezone.