Milestone deadline timestamp broken #6206

Closed
opened 2025-11-02 06:48:20 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @noerw on GitHub (Oct 23, 2020).

Description

Milestone deadlines are not parsed correctly.
This applies both to newly created milestones & existing milestones where the timestamp was ok before.
v1.13.0-rc1 doesnt seem to have this issue.

Screenshots

Screenshot from 2020-10-23 14-23-23

Originally created by @noerw on GitHub (Oct 23, 2020). - Gitea version (or commit ref): 1.14.0+dev-12-gcb171dbd5 - Git version: ? - Operating system: ? <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) https://gitea.com/gitea/tea/milestone/1310 - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description Milestone deadlines are not parsed correctly. This applies both to newly created milestones & existing milestones where the timestamp was ok before. v1.13.0-rc1 doesnt seem to have this issue. ## Screenshots ![Screenshot from 2020-10-23 14-23-23](https://user-images.githubusercontent.com/7880552/97012640-9610cc80-1537-11eb-852b-c7d99f92bb08.png)
GiteaMirror added the issue/staletype/bug labels 2025-11-02 06:48:20 -06:00
Author
Owner

@stale[bot] commented on GitHub (Dec 24, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Dec 24, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6206