[
https://issues.apache.org/jira/browse/VCL-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285712#comment-14285712
]
Karl Vollmer commented on VCL-807:
----------------------------------
Potentially forcing +0 (UTC) for DB /Backend / Webserver stored times would
make sense so they can't accidentally get offset, then just translate when
displaying to the users / logging. The concern there is if we had a management
node located in Newfoundland (+30 TZ) and their system default TZ would be off
from a webserver hosted in Nova Scotia.
> indicate timezone on schedules / reservations
> ---------------------------------------------
>
> Key: VCL-807
> URL: https://issues.apache.org/jira/browse/VCL-807
> Project: VCL
> Issue Type: Improvement
> Components: web gui (frontend)
> Affects Versions: 2.3.2
> Environment: Client computer is in GMT-4, Server is in GMT-5
> Reporter: Karl Vollmer
> Priority: Trivial
>
> The times listed on the reservation, and on the schedule are related to the
> server time, not the local time of the client using the interface. This
> becomes an issue if we have users in different timezones, Atlantic Canada has
> ADT/AST and NDT/NST (:30 min earlier)
> If possible detecting the local user timezone, or providing timezone as a
> user preference.
> In addition to that indicating the Timezone/Offset value on all indications
> of time would help in troubleshooting why schedules are claiming no available
> resources / reservation times are off :D
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
