Due is shown incorrectly

[mrdunski]

Description

The issue is here: https://try.gitea.io/pan_dunski/test/issues/1

I've chosen due as 2022-12-02 but after save it is converted to 2022-12-03

My timezone is CEST

Gitea Version

1.18.0+rc1

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

No response

Operating System

No response

How are you running Gitea?

I'm using official chart with the following values:

image:
  repository: gitea/gitea
  pullPolicy: Always
  tag: "1.18.0-rc1"

Database

PostgreSQL

[wolfogre]

Yeah, it's caused by mismatch timezones.

The exact due date is Fri, 02 Dec 2022 23:59:59 +0000, it's "+0000" because the timezone of try.gitea.io is UTC. and that means "2022-12-03" in CEST.

I know it's confusing, but it's not complicated to solve it, just set the timezone of the container to your preferred one.

[mrdunski]

I think that's not the point. It uses different strategy (different time zone) in the time picker and the field. It is not confusing, but incorrect.

This is something new in 1.18, 1.17 works correctly with the same settings.

[wolfogre]

In 1.17 they did use the same timezone, until #21440.

@yardenshoham Any ideas?

[yardenshoham]

Your explanation is correct. It's a timezone mismatch issue. The problem is that the Due Date field input uses UTC while it should be localized.