From reading other related threads, I understand your current approach: ‘each user ‘thinks’ in their timezone’. And in a lot of cases that makes sense! But for some use cases you need to be able to set a time for a specific timezone, where all Fibery users see the same time.
In our case we’re developing an order management system and when the customer submits an order, they supply a specific time along with their order, which is relative to their timezone. Since we’re not able to set the supplied time in the customer’s timezone (server-side it gets set to UTC), this time / timzone needs to be unified across all Fibery users sitting in different timezones. Otherwise each Fibery user looking at that particular order will see a different time - that actually doesn’t reflect the truth (the customer’s timezone)! And when they try to coordinate this amongst each other or with the customer, it will create a royal mess, because each user sees it in their timezone instead of the customers.
Are any others interested in this feature as well? What use case would this solve for you?
Just came across this as I was dealing with timezones… again.
Here’s what I would like (and I think it would align with @antoniokov’s post):
In field labels show a little timezone info, e.g. in a property called Timestamp, the table header would display Timestamp (UTC+8) so everybody knows that this is a local time.
Allow me to define Date & Time property to always display as UTC for everybody. Useful for things like deployment timestamps, etc. and in that case it could show a small (UTC) next to the label.
It just makes things explicit for all users on what’s going on.
I also recently contacted support because we are going to onboard our first two digital nomad clients next month. For them all time zone issues are also really important.
I’m really hoping this will be solved one day
And in the meantime this will prevent questions and a lot of frustrations I think.