Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0016301Openbravo ERPB. User interfacepublic2011-03-15 12:562012-08-09 11:55
Reporterplujan 
Assigned Tomtaal 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0016301: Some invalid dates are misinterpred by the Date Filter
DescriptionIf I enter a non valid date, like 31st of February, it is wrongly interpreted as some day of March. See attach.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0021335 closed AugustoMauch Range must disappear after manually clearing the date filter field in the grid 
Attached Filespng screenshot-13.png (7,359) 2011-03-15 12:56
https://issues.openbravo.com/file_download.php?file_id=3685&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2011-03-15 12:56plujanNew Issue
2011-03-15 12:56plujanAssigned To => mtaal
2011-03-15 12:56plujanFile Added: screenshot-13.png
2011-03-15 12:56plujanModules => Core
2011-03-16 08:23alostaleTarget Version => 3.0RC6
2011-03-16 08:30alostaleStatusnew => scheduled
2011-04-04 10:31mtaalTarget Version3.0RC6 => 3.0RC7
2011-04-27 15:29hgbotCheckin
2011-04-27 15:29hgbotNote Added: 0036128
2011-04-27 15:29hgbotStatusscheduled => resolved
2011-04-27 15:29hgbotResolutionopen => fixed
2011-04-27 15:29hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/2c4261aece1412ac92c5eafd37605442f60abdb3 [^]
2011-05-12 13:27hudsonbotCheckin
2011-05-12 13:27hudsonbotNote Added: 0036776
2011-05-13 13:03dbazNote Added: 0036964
2011-05-13 13:03dbazStatusresolved => new
2011-05-13 13:03dbazResolutionfixed => open
2011-05-13 13:29mtaalTarget Version3.0RC7 => 3.0MP0
2011-05-16 08:57alostaleStatusnew => scheduled
2011-05-23 11:34plujanTarget Version3.0MP0 => 3.0MP1
2011-06-22 19:41dmitry_mezentsevTarget Version3.0MP1 => 3.0MP3
2011-08-31 09:48mtaalTarget Version3.0MP3 => 3.0MP4
2011-09-19 09:16mtaalTarget Version3.0MP4 => 3.0MP5
2011-10-25 08:00mtaalTarget Version3.0MP5 => 3.0MP6
2011-11-15 10:21iperdomoTarget Version3.0MP6 =>
2012-07-31 16:55AugustoMauchNote Added: 0051035
2012-08-09 11:51rgorisRelationship addedrelated to 0021335
2012-08-09 11:55AugustoMauchStatusscheduled => resolved
2012-08-09 11:55AugustoMauchResolutionopen => fixed
2012-08-09 11:55AugustoMauchNote Added: 0051192
2012-08-09 11:55AugustoMauchStatusresolved => closed

Notes
(0036128)
hgbot   
2011-04-27 15:29   
Repository: erp/devel/pi
Changeset: 2c4261aece1412ac92c5eafd37605442f60abdb3
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Wed Apr 27 15:28:55 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/2c4261aece1412ac92c5eafd37605442f60abdb3 [^]

Fixes issue 16301: Some invalid dates are misinterpred by the Date Filter

---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-formitem-widgets.js
---
(0036776)
hudsonbot   
2011-05-12 13:27   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/c40e579fcd38 [^]

Maturity status: Test
(0036964)
dbaz   
2011-05-13 13:03   
If I put in the selection range, for example, 32-03-2011, nothing happens (it seems that the system realizes that the date is not correct)

If I put, 31-02-2011, it converts to 03-03-2011
If I put, 31-04-2011, it converts to 01-05-2011

So it seems that allow values are to 31-XX and then if the month doesn't fit it moves to next month.
(0051035)
AugustoMauch   
2012-07-31 16:55   
I think that it is desirable that if the user enters 31-04-2011, the date is automatically converted to 01-05-2011. It is a very useful mistake to miscount the number of days in a month. If today is 29-04-2012 and I want to enter a date two days after today, I might enter 31-04-2012. That date does not exist, but 01-05-2012 does, and is the date meant by the user.

This behaviour is also used by the date parsing in javascript:

new Date(Date.parse("Apr 31, 2012"));
Tue May 01 2012 00:00:00 GMT+0200 (CEST)

new Date(Date.parse("Apr 32, 2012"));
Invalid Date
(0051192)
AugustoMauch   
2012-08-09 11:55   
I have talked to Rob Goris, and we have agreed that the current behaviour is correct, so the issue can be closed.