-
-
To reply myself so I can help others. It turned out the problematic field was a custom field I had created long ago which was of a type Date/Time. In the custom filed settings there is a way to enable “Show date/time relative to user’s timezone” which solved the issue.
-
You must be logged in to reply to this topic.