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.

[palmen]

Exactly, 4h is always 4h no matter what timezone, that's why we have quite a big issue here. Sometimes when you enter 0 in downtime it changes it to 23h as well.

As far as I know there is no other field impacting this custom made downtime field, and I've seen the exact same behaviour in another instance with users based in different timezones.

[palmen]

This is what it look like in history in one of the cases, the first and second update is correct, but for some reason the last update changes the duration to 23:30 from 00:30 without the user changeing the value.

This is happening for a lot of different users but not for everyone. I've seen it myself when testing but don't know how to reproduce the issue, it only happens some times.

[Anurag Tripathi]

Id be doing the following

1) check the dictionary to see if there is anything out of the ordinary (attributes, calculated/calculation etc)

2) check the scripts to see if this field is being changed by any(BR, Client scripts, ui policies etc)

3) create a new duration field, fill the same value in existing and the new one and see if the new one also shows this behavior.

PS:- I HATE GHOST ISSUES

[palmen]

It's basicly what I've done already

1) Nothigng on the dictionary since the field was created yesterday and I got this issue first time testing it

2) Since it's a brand new field I'm 100% sure no scripts will target this field

3) I just created this duration field in instance X. I've had another duration field in another instance (Y) with the exact same behaviour.

I thought we had done something in instance Y since we've had the issue there in some cases (doesn't always happen), when I got the same behaviour for a new field in instance X I came to the conclussion there must be somethign "wrong" here, but can't find what it is.

Only problem is I don't know how to reproduce it. In instance Y I've a lot of cases where it has happened but haven't seen it up front when it happends. In instance X it happened to me while testing yesterday when I inpersonated a user in another timezone so I've seen it myself.

[Anurag Tripathi]

Let me try to replicate this in my personal instance.