Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0025602Openbravo ERPA. Platformpublic2014-01-30 09:342014-02-12 18:29
Reporteregoitz 
Assigned ToAugustoMauch 
PriorityimmediateSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target Version3.0PR14Q2Fixed in Version3.0PR14Q2 
Merge Request Status
Review Assigned Toshankarb
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression levelProduction - Confirmed Stable
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0025602: The time fiels are modified after save a record
DescriptionAfter save a record where exits a time field, the time is changes after click on save.
Steps To Reproduce-Go to process request window
-Create a new record
-Define the request as scheduled to show the start_time field
-Define a start_time
-Save
-Refresh
*See that the value is changed

-If you have previously shown the start_time field on grid view the error does not happen
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0025274 closed AugustoMauch The time fields are not working properly 
blocks defect 00258273.0PR14Q2 closed AugustoMauch Time fields are not working properly in timezones with negative offsets 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-01-30 09:34egoitzNew Issue
2014-01-30 09:34egoitzAssigned To => AugustoMauch
2014-01-30 09:34egoitzModules => Core
2014-01-30 09:34egoitzResolution time => 1391727600
2014-01-30 09:34egoitzTriggers an Emergency Pack => No
2014-01-30 09:36egoitzSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=5383#r5383
2014-01-30 09:37egoitzRegression level => Production - Confirmed Stable
2014-01-30 09:37egoitzRelationship addedrelated to 0025274
2014-01-31 11:41AugustoMauchIssue Monitored: shankarb
2014-01-31 11:41AugustoMauchReview Assigned To => shankarb
2014-01-31 11:42hgbotCheckin
2014-01-31 11:42hgbotNote Added: 0063823
2014-01-31 11:42hgbotStatusnew => resolved
2014-01-31 11:42hgbotResolutionopen => fixed
2014-01-31 11:42hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/adf0b763ad3674b9f14cc06c5d80e3aee4b24cc5 [^]
2014-02-03 04:22shankarbNote Added: 0063844
2014-02-03 04:22shankarbStatusresolved => closed
2014-02-03 04:22shankarbFixed in Version => 3.0MP32
2014-02-12 18:29hudsonbotCheckin
2014-02-12 18:29hudsonbotNote Added: 0064142
2014-02-25 11:11AugustoMauchRelationship addedblocks 0025827

Notes
(0063823)
hgbot   
2014-01-31 11:42   
Repository: erp/devel/pi
Changeset: adf0b763ad3674b9f14cc06c5d80e3aee4b24cc5
Author: Augusto Mauch <augusto.mauch <at> openbravo.com>
Date: Fri Jan 31 11:41:31 2014 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/adf0b763ad3674b9f14cc06c5d80e3aee4b24cc5 [^]

Fixes issue 25602: Time fields behave properly when record is refreshed

The value that is passed to TimeUIDefinition.convertToClassicString is taken from the database, so is stored in the server local timezone. It needs to be conv
erted to UTC before formatting it in a String

---
M modules/org.openbravo.client.kernel/src/org/openbravo/client/kernel/reference/TimeUIDefinition.java
---
(0063844)
shankarb   
2014-02-03 04:22   
Code reviewed and verified in pi changeset dd19b027b406.
(0064142)
hudsonbot   
2014-02-12 18:29   
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/d1a5bb862230 [^]
Maturity status: Test