Comment 0 for bug 992259
Revision history for this message
| Don Kirkby (donkirkby) wrote Calculating datetime from date cause timezone issues in sales order | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This may be similar to the hr_timesheet_sheet bug 943091, and is certainly related to the change in 6.1 to use UTC on all datetime fields in the server, as described in bug 925361. It sounds like the context_today() method helps when calculating date fields based on the current date, but how can we calculate a datetime based on a pure date?
The example scenario I have run into is confirming a sales order.
1. My user timezone is -7:00 PDT.
2. I create a sales order with date 2012-05-01.
3. I confirm the sales order, and look at the picking list.
Expected behaviour: the picking list should either have order date 2012-05-01 00:00:00. Also acceptable would be to ignore the sales order's order date, and use the current datetime for the picking list's order date as it did in version 5.0
Actual behaviour: the picking list has order date 2012-04-30 17:00:00. This is 2012-05-01 midnight UCT adjusted for the user's time zone.
I am running 6.1.0 on Ubuntu 10.04.