Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0025827 | Openbravo ERP | A. Platform | public | 2014-02-25 11:11 | 2014-02-25 20:14 |
|
Reporter | AugustoMauch | |
Assigned To | AugustoMauch | |
Priority | immediate | Severity | major | Reproducibility | have not tried |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | | |
Target Version | 3.0PR14Q2 | Fixed in Version | 3.0PR14Q2 | |
Merge Request Status | |
Review Assigned To | shankarb |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | Production - Confirmed Stable |
Regression date | 2013-09-11 |
Regression introduced in release | |
Regression introduced by commit | https://code.openbravo.com/erp/devel/pi/rev/290c9b12a211 [^] |
Triggers an Emergency Pack | No |
|
Summary | 0025827: Time fields are not working properly in timezones with negative offsets |
Description | When a time field is saved from a timezone with a negative offset, its value is not being properly shown in the client. |
Steps To Reproduce | From a timezone with negative offset (i.e. Monreal, GMT-5):
- Open Process Request
- Start creating a new record in form view
- Set Run Later in the Timing Combo
- Set 10:00:00 in the Start Time field
- Save. The proper value will be saved in the database, but the value shown to the user will be wrong.
- Refresh. The proper value will be shown |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | depends on | defect | 0025274 | | closed | AugustoMauch | The time fields are not working properly | depends on | defect | 0025602 | 3.0PR14Q2 | closed | AugustoMauch | The time fiels are modified after save a record | related to | defect | 0025838 | 3.0PR14Q2 | closed | AugustoMauch | Time fields are still not working properly in timezones with negative offsets |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2014-02-25 11:11 | AugustoMauch | New Issue | |
2014-02-25 11:11 | AugustoMauch | Assigned To | => AugustoMauch |
2014-02-25 11:11 | AugustoMauch | Modules | => Core |
2014-02-25 11:11 | AugustoMauch | Triggers an Emergency Pack | => No |
2014-02-25 11:11 | AugustoMauch | Relationship added | depends on 0025274 |
2014-02-25 11:11 | AugustoMauch | Relationship added | depends on 0025602 |
2014-02-25 11:13 | AugustoMauch | Regression level | => Production - Confirmed Stable |
2014-02-25 11:13 | AugustoMauch | Regression date | => 2013-09-11 |
2014-02-25 11:13 | AugustoMauch | Regression introduced by commit | => https://code.openbravo.com/erp/devel/pi/rev/290c9b12a211 [^] |
2014-02-25 11:19 | AugustoMauch | Issue Monitored: shankarb | |
2014-02-25 11:19 | AugustoMauch | Review Assigned To | => shankarb |
2014-02-25 11:22 | hgbot | Checkin | |
2014-02-25 11:22 | hgbot | Note Added: 0064558 | |
2014-02-25 11:22 | hgbot | Status | new => resolved |
2014-02-25 11:22 | hgbot | Resolution | open => fixed |
2014-02-25 11:22 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/7feaacbc88b193ba517168f1ed718849d67db313 [^] |
2014-02-25 14:04 | shankarb | Note Added: 0064565 | |
2014-02-25 14:04 | shankarb | Status | resolved => closed |
2014-02-25 14:04 | shankarb | Fixed in Version | => 3.0MP32 |
2014-02-25 20:14 | hudsonbot | Checkin | |
2014-02-25 20:14 | hudsonbot | Note Added: 0064592 | |
2014-02-26 09:51 | AugustoMauch | Relationship added | related to 0025838 |
Notes |
|
(0064558)
|
hgbot
|
2014-02-25 11:22
|
|
Repository: erp/devel/pi
Changeset: 7feaacbc88b193ba517168f1ed718849d67db313
Author: Augusto Mauch <augusto.mauch <at> openbravo.com>
Date: Tue Feb 25 11:21:33 2014 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/7feaacbc88b193ba517168f1ed718849d67db313 [^]
Fixes issue 25827: Time fields work properly in timezones with negative offsets
Depending on who calls the formSaved function of OBTimeItem, the provided time can be already converted to the client local time or not. To know the time has a
lready been converted, the function used to check if the full year of the time was 1970. If that was the case, then the time was converted from UTC to local ti
me.
The problem is that if the user is working from a timezone with negative offset the full year will not be 1970, but 1969. This has been fixed by replacing data
[this.name].getFullYear() === 1970 with data[this.name].getFullYear() <= 1970
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/form/formitem/ob-formitem-time.js
---
|
|
|
(0064565)
|
shankarb
|
2014-02-25 14:04
|
|
Code reviewed and verified in pi changeset 7feaacbc88b1. |
|
|
|
|