[Bug]: Due date increments by four hours upon saving #773

Closed
opened 2026-02-04 21:17:48 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @controlaltnerd on GitHub (Aug 3, 2025).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

Brave, Chrome, Safari

Current behavior

On any card, when I set or update the due date or time, the time as shown in the date picker pop-up is incremented by four hours when I click the Save button. It doesn't happen if the date or time is not modified, i.e. opening the pop-up and just clicking Save won't cause it to change. It only increments when there is an actual change to either the date or time.

Desired behavior

The time should not change when clicking Save.

Steps to reproduce

Open any card, update the date or time, then click Save and observe the time change.

Other information

No response

Originally created by @controlaltnerd on GitHub (Aug 3, 2025). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? Brave, Chrome, Safari ### Current behavior On any card, when I set or update the due date or time, the time as shown in the date picker pop-up is incremented by four hours when I click the **Save** button. It doesn't happen if the date or time is not modified, i.e. opening the pop-up and just clicking **Save** won't cause it to change. It only increments when there is an actual change to either the date or time. ### Desired behavior The time should not change when clicking **Save**. ### Steps to reproduce Open any card, update the date or time, then click **Save** and observe the time change. ### Other information _No response_
Author
Owner

@meltyshev commented on GitHub (Aug 4, 2025):

Hi! Thanks for reporting this. To be honest, I couldn't reproduce it - when I change the time and click save, it saves the correct value.

I think the problem might be related to the TZ environment variable - it should always be set to UTC for everything to work properly (btw, we've already fixed this, but the new version hasn't been released yet). If that's the case, please try setting the TZ=UTC and restarting the instance. It's hard to say what else could be causing the issue without seeing your full configuration.

@meltyshev commented on GitHub (Aug 4, 2025): Hi! Thanks for reporting this. To be honest, I couldn't reproduce it - when I change the time and click save, it saves the correct value. I think the problem might be related to the `TZ` environment variable - it should always be set to `UTC` for everything to work properly (btw, we've already fixed this, but the new version hasn't been released yet). If that's the case, please try setting the `TZ=UTC` and restarting the instance. It's hard to say what else could be causing the issue without seeing your full configuration.
Author
Owner

@controlaltnerd commented on GitHub (Aug 4, 2025):

@meltyshev thank you, that did indeed fix the issue.

@controlaltnerd commented on GitHub (Aug 4, 2025): @meltyshev thank you, that did indeed fix the issue.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#773