Opened 19 years ago
Closed 18 years ago
#1633 closed enhancement (fixed)
Milestones due a day too early
| Reported by: | anonymous | Owned by: | Christopher Lenz |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.9.1 |
| Component: | roadmap | Version: | 0.8.1 |
| Severity: | normal | Keywords: | |
| Cc: | pacopablo@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Milestones are considered "closed" (in 0.8.1) or "late" (in trunk) at midnight of the date specified as the due date.
The result is having to set the due date one day later than desired if you want the milestone to be shown on the due date itself (or not be marked late, as of trunk).
It would make more sense to either allow a time be specified for the due date of a milestone, ie '06/04/05 17:30' or set the completion time to 11:59 on the due date as opposed to 00:00
Attachments (0)
Change History (5)
comment:1 by , 18 years ago
| Milestone: | → 0.9.1 |
|---|---|
| Status: | new → assigned |
| Summary: | Include time in milestone due date → Milestones due a day too early |
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 by , 18 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
I think it might be better to have the milestone display as due today on the due date, due in x (days/week/etc) before the due date, and x (days/weeks/etc) late after the due date. It seems to me that it would fit better into the concept of a milestone having a due date rather than a due time.
Fixed in [2457] and [2458].