Defect #9662
closed
Start date setted to 5000-01-01
0%
Description
I don't know why, but sometimes when i woun't set start date, redmine sets it on his own way to 5000-01-01, and i'm unable to remove it.
I've noticed this bug with clean Redmine and with patch which doesn't set start date to current date in new issues.
Server: Windows 2008 R2
Updated by Etienne Massip about 13 years ago
- Affected version (unused) set to devel
Which database?
No plugins?
Updated by Mischa The Evil about 13 years ago
FWIW: I've never seen this behavior on vanilla Redmines.
Updated by Szymon Nowak about 13 years ago
MySQL, Apache - BitNami Stack but on Windows 2008 R2 as i've mentioned
Etienne Massip wrote:
Which database?
No plugins?
Updated by Etienne Massip about 13 years ago
- Resolution set to Cant reproduce
Szymon Nowak wrote:
redmine sets it on his own way to 5000-01-01
In new issue screen? In DB?
I've noticed this bug with clean Redmine and with patch which doesn't set start date to current date in new issues.
You did patch a stable release?
Mischa The Evil wrote:
FWIW: I've never seen this behavior on vanilla Redmines.
I've never seen such a buggy date (year 5000???) neither :|
And MySQL CI tests passed...
Updated by Jean-Philippe Lang about 13 years ago
- Status changed from New to Closed
Updated by Vasiliy Zaytcev over 12 years ago
i have removed plugin redmine_due_date_by_default and the problem has been fixed