Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues and Milestones due today are marked as overdue #5566

Closed
1 of 7 tasks
znegva opened this issue Dec 19, 2018 · 1 comment · Fixed by #5568
Closed
1 of 7 tasks

Issues and Milestones due today are marked as overdue #5566

znegva opened this issue Dec 19, 2018 · 1 comment · Fixed by #5568
Labels

Comments

@znegva
Copy link
Contributor

znegva commented Dec 19, 2018

  • Gitea version (or commit ref): 1.6.1
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Issues and Milestones can get an Due date.
If the due date is set to the current day it gets supplemented by the text Overdue.
In listings Overdue entries get their Due-Date colored red.

In fact if something is overdue, it should have been done before now - if something is due today I still have time to do it 😄

My suggestion would be to call something overdue if it really was due to yesterday or before.
And I would suggest to add an additional state like Due today (which could be colored maybe yellow in listings)

Screenshots

screenshot 2018-12-19 at 14 59 37

@kolaente
Copy link
Member

This is because due dates are saved as unix timestamps. So when you save a due date for lets say the 21.12.2018, it is saved as 21.12.2018 00:00. So, if it's the 21.12.2018 15:00, it makes perfect sense to compare it that way. IMHO we should change it when saving.

jonasfranz pushed a commit that referenced this issue Jan 1, 2019
* Due date time of issues and milestones is set to 23:59:59

* Add docs

* make gen swagger

* fix swagger gen
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants