[Bug]: Due date timezone incorrect #896

New Issue

OVERLORD · 2026-02-04T21:34:44+03:00

OVERLORD commented

2026-02-04 21:34:44 +03:00

Originally created by @sumnerboy12 on GitHub (Jan 11, 2026).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

Chrome

Current behavior

My browser is set to New Zealand timezone. If I set a due date on a card I select 12:00 on 11 Jan 2026 and after confirming, the UI is showing a due date on the card of 23:00 on 10 Jan 2026, which looks like UTC timezone.

I can't see anything in the docs or sample .env file with a TZ setting.

Is there a way to configure the timezone correctly?

Desired behavior

No response

Steps to reproduce

Using a browser in non-UTC timezone, enter a due date for a card.

Other information

No response

Originally created by @sumnerboy12 on GitHub (Jan 11, 2026). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? Chrome ### Current behavior My browser is set to New Zealand timezone. If I set a due date on a card I select 12:00 on 11 Jan 2026 and after confirming, the UI is showing a due date on the card of 23:00 on 10 Jan 2026, which looks like UTC timezone. I can't see anything in the docs or sample .env file with a TZ setting. Is there a way to configure the timezone correctly? ### Desired behavior _No response_ ### Steps to reproduce Using a browser in non-UTC timezone, enter a due date for a card. ### Other information _No response_

OVERLORD commented

2026-02-04 21:34:50 +03:00

@meltyshev commented on GitHub (Jan 11, 2026):

Hey! Thanks for reporting this. I think the issue might be that the server has a TZ environment variable set, which overrides the database's default timezone and causes dates to be converted before they're saved.

We recently made several changes around this by removing the TZ env variable. Previously, it always had to be set to UTC for the app to work correctly, and that was a common source of issues. Going forward, this should be handled automatically without relying on TZ. That said, the final v2 release isn't out yet - we're still working on it, and it should be available in a few days.

For now, as a workaround, you can try adding TZ=UTC to your docker-compose.yml (under the planka service), or if you're using a manual installation, add TZ=UTC to the .env file instead. If the problem persists, please let us know. You can also try the Pro demo on our website and set a due date there - this version already includes the change, so we'll be able to confirm if the issue will be resolved in the new release.

@meltyshev commented on GitHub (Jan 11, 2026): Hey! Thanks for reporting this. I think the issue might be that the server has a `TZ` environment variable set, which overrides the database's default timezone and causes dates to be converted before they're saved. We recently made several changes around this by removing the `TZ` env variable. Previously, it always had to be set to `UTC` for the app to work correctly, and that was a common source of issues. Going forward, this should be handled automatically without relying on `TZ`. That said, the final v2 release isn't out yet - we're still working on it, and it should be available in a few days. For now, as a workaround, you can try adding `TZ=UTC` to your `docker-compose.yml` (under the planka service), or if you're using a manual installation, add `TZ=UTC` to the `.env` file instead. If the problem persists, please let us know. You can also try the Pro demo on our website and set a due date there - this version already includes the change, so we'll be able to confirm if the issue will be resolved in the new release.

OVERLORD commented

2026-02-04 21:34:53 +03:00

@sumnerboy12 commented on GitHub (Jan 11, 2026):

Thanks so much for the prompt reply - I tried adding TZ=UTC and now everything is working - fantastic!! Thanks again, and thanks for sharing such a wonderful tool!!

@sumnerboy12 commented on GitHub (Jan 11, 2026): Thanks so much for the prompt reply - I tried adding TZ=UTC and now everything is working - fantastic!! Thanks again, and thanks for sharing such a wonderful tool!!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#896