You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the user profile page in a self-hosted instance, when selecting a user's timezone, all US timezones are one hour off from what they currently should be. See example below.
Note that US/Eastern time is listed as GMT-04:00. Currently, it is actually GMT-05:00. All US timezones are similarly incorrect. The displayed GMT offsets would be valid if Daylight Savings Time were currently in effect - but it is not.
The actual behavior of the system is correct - for example, when I log in and go to the workspace homepage, the time displayed is actually the correct local time, as selected by my current timezone. It is just the GMT offsets displayed in the profile page, in the timezone selection dialog, that are incorrect.
Steps to reproduce
Log into a Plane instance.
Click on the user avatar in the left-side navigation panel, and select "Settings"
Click on the drop-down arrow for the "Timezone" field.
Note that GMT offsets for all offered US timezones are off by one hour.
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
v0.24.1
The text was updated successfully, but these errors were encountered:
If it matters, my Plane instance is deployed on Arch Linux, updated as of earlier today. (As Arch Linux is a "rolling release" distro, there is no release version number, per se - but the installed kernel, after applying all available updates to my system earlier today, is 6.12.8-arch1-1.)
Is there an existing issue for this?
Current behavior
In the user profile page in a self-hosted instance, when selecting a user's timezone, all US timezones are one hour off from what they currently should be. See example below.
Note that US/Eastern time is listed as GMT-04:00. Currently, it is actually GMT-05:00. All US timezones are similarly incorrect. The displayed GMT offsets would be valid if Daylight Savings Time were currently in effect - but it is not.
The actual behavior of the system is correct - for example, when I log in and go to the workspace homepage, the time displayed is actually the correct local time, as selected by my current timezone. It is just the GMT offsets displayed in the profile page, in the timezone selection dialog, that are incorrect.
Steps to reproduce
Environment
Production
Browser
Google Chrome
Variant
Self-hosted
Version
v0.24.1
The text was updated successfully, but these errors were encountered: