Dates Closed editor: User input not monitored
Bug #888604 reported by
Jim Frey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
2.2 |
Won't Fix
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned | ||
2.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When users enter date spans in to the Closed Dates Editor, the system doesn't perform checks to verify accuracy. It is possible to enter a CLOSE_END date that is less than/prior to the CLOSE_START date. For example, when creating a record listing a closing over New Year, users may enter CLOSE_START as "2011-12-31" and CLOSE_END as "2011-01-01" (a whole year earlier).
Changed in evergreen: | |
importance: | Undecided → Medium |
milestone: | none → 2.4.0-alpha |
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → none |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Should have mentioned: Using EG version 1.6.2+