Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0029691Openbravo ERPB. User interfacepublic2015-04-23 19:352015-04-29 09:31
Reportercaristu 
Assigned Todbaz 
PriorityimmediateSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target Version3.0PR15Q2Fixed in Version3.0PR15Q2 
Merge Request Status
Review Assigned Toalostale
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression levelProduction - Confirmed Stable
Regression date2014-05-15
Regression introduced in release3.0PR14Q3
Regression introduced by commithttp://code.openbravo.com/erp/devel/pi/rev/43e598987eb706d4eac832d474b84a1d0b7ac958 [^]
Triggers an Emergency PackNo
Summary0029691: Is not possible to set the hour 12 in DateTime fields
DescriptionIs not possible to set the hour 12 in DateTime fields, it is always being converted to 0 when the field loses the focus.
Steps To Reproduce1) Go to the Work Effort window and create a new record in the header
2) Navigate to the Production Run tab
3) In the Starting Time field, type date and a hour with 12 for example: 04-23-2015 12:26:05
4) Move to another field. Notice that the Starting Time is changed to 04-23-2015 00:26:05
Proposed SolutionThe parseEditorValue method uses the OB.Utilities.Date.OBToJS which is doing this conversion waiting for a PM indicator. As this indicator is not included it then makes the replacement.
Additional Information
TagsApproved
Relationships
blocks defect 0029687 closed dbaz Is not possible to set the hour 12 in DateTime fields 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-04-24 11:43alostaleTypedefect => backport
2015-04-24 11:43alostaleTarget Version => 3.0PR15Q2
2015-04-24 14:12dmitry_mezentsevTag Attached: Approved
2015-04-28 12:19dbazReview Assigned To => alostale
2015-04-28 12:53hgbotCheckin
2015-04-28 12:53hgbotNote Added: 0076829
2015-04-28 12:53hgbotStatusscheduled => resolved
2015-04-28 12:53hgbotResolutionopen => fixed
2015-04-28 12:53hgbotFixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR15Q2/rev/e8bf5ea8a0380c59908c83e62bed7ab59bddee6f [^]
2015-04-29 09:31alostaleNote Added: 0076849
2015-04-29 09:31alostaleStatusresolved => closed
2015-04-29 09:31alostaleFixed in Version => 3.0PR15Q2

Notes
(0076829)
hgbot   
2015-04-28 12:53   
Repository: erp/backports/3.0PR15Q2
Changeset: e8bf5ea8a0380c59908c83e62bed7ab59bddee6f
Author: David Baz Fayos <david.baz <at> openbravo.com>
Date: Tue Apr 28 12:07:49 2015 +0200
URL: http://code.openbravo.com/erp/backports/3.0PR15Q2/rev/e8bf5ea8a0380c59908c83e62bed7ab59bddee6f [^]

Fixed issue 29691: DateTime now works ok with 12:XX:XX times

The root of the problem was that there was a 'typo' and the
'minus' sign was missing in the 'if' statement in charge
of evaluate if it was in 24h mode or not. This was used later
to substract 12h to the entered date if this was in the
12:XX:XX form, change that obviously doesn't apply in the
24h mode

---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/utilities/ob-utilities-date.js
---
(0076849)
alostale   
2015-04-29 09:31   
code reviewed

tested with 12 and 24 hour time format in grid and form views