Well I am guessing it simplified time widgets in the UI. It could be fixed with some extra effort, but apparently no implementation had an issue with that yet (all having servers and clients in the same time zone).
This is a known limitation. We were running into issues with time zone differences between client machines and the server when building out the new appointment scheduling UI and there was no obvious, easy fix, so we made the requirement that that the client machine and the server need to be in the same time zone–which should be true anyway for 98% of our current use cases. However, as @michael points out this is less-than-ideal for a generic appointment solution. If somebody has time to ticket and fix I’m all for it. I believe @darius may be tackling this on a broader level.
@natalia, to check, what do you think would be the correct behavior? For example imagine that the server is at a hospital in New York, and you’re logging in from a computer whose timezone is set to Poland. How should this affect the appointment scheduling screens? (I know what I think should happen, but I’m curious what others think.)
I think that when I am in Poland and I want to schedule the appointment in USA, it shouldn’t affect my screen, because I have to be in USA on this appointment on USA time zone, not Polish time zone. It shouldn’t matter from which part of the world I schedule the appointment.
I’m not quite sure if you have the opportunity to solve the problem (its not really an error in my eyes) is yet but one way that I found of overcoming the situation is to make sure that the server (which in my case is located in a data centre offshore) is the same time zone as the client machines accessing the server.
I would be very reluctant to try and update every single time zone and time on each of the client machines as this will take a lot of time and be quite painful for the end-user.
On a Debian based (such as Ubuntu) Linux server you can change the time zone relatively easily.
Step one find out what time zone is available to you by typing the following command.
root@server:# timedatectl list-timezones
(scroll down using the arrow keys to find the appropriate time zone)