Sessions listed in tlwebadm have the fields "Created" and "Last connection" which show a time and date. Both of these are shown in the local time of the server (technically the tlwebadm process), but this detail is not mentioned in the user interface or the documentation.
For many users, this might be fine, as all of their users and systems are in the same time zone. But some users might have people from multiple time zones looking at this interface. E.g. because they are a global organization, or they are in a country with multiple time zones, like the US.
Note that the time zone for the given time might be different from the current time zone, if the server is affected by daylight savings time. The code therefore needs to be careful about how it determines the time zone.
Timestamps in tlwebadm now include a time zone tag. This is fixed and verified.
The verification was done by starting two sessions in different timezones.
> Timezone on server: CET
* Session 1 was started. The timestamp for session creation reports correct time with timezone CET. This is correct behavior.
With the session 1 still present, the clock on the server was then set six months forward, such that the expected timezone then should be CEST.
> Timezone on server: CEST
* Session 1 still shows the same timestamp with timezone CET. This is correct behavior.
* Session 2 was started. The timestamp for session creation reports correct time with timezone CEST. This is correct behavior.