Due Date Format for Milesones

[tcpluess]

The date formats for milestones are inconsistent.
For the due date, the mm/dd/yyyy format is used, whereas the normal yyyy-mm-dd is used in the milestones overview.
There should be an option to change the date format.

• Gitea version (or commit ref): 1.14.1
• Git version: 2.30.2
• Operating system: Linux
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (any repo)
  • No
• Log gist:

Description

...

Screenshots

[silverwind]

The date input is locale-aware but our date/time rendering is not. This will require a big overhaul of our timestamp rendering and would likely require it to be done in JavaScript, like Github does.

[tcpluess]

OK I can understand that this change will not happen in the near future. However on the other hand we could argue that there is an actual ISO standard about how dates should be written:

https://en.wikipedia.org/wiki/ISO_8601

in that case it would not be necessary to use locale-aware date/time format, one could just stick to the ISO standard.

[silverwind]

I think generally we want to render timestamps in relative format (which should be locale-independent strings) with absolute date in a tooltip (which can be locale-dependant).

Thought I do see a reason to render Milestone Due dates as absolute, Github does it too (Due by July 29, 2021).

[yardenshoham]

Fixed in #23988?

[silverwind]

I'd say so as we now render in the user's OS preference.

[delvh]

Isn't this issue actually talking about #24055 which was never merged and should thus be reopened?

[lunny]

It's another date format used for due dates.

[yardenshoham]

#24055 was replaced by #24275 so I think we can close it