openerp-india team mailing list archive

[Don Kirkby <992259@xxxxxxxxxxxxxxxxxx>]

Thanks for trying to reproduce it, Ravish.

Please check that your OpenERP user time zone is set to PDT. In the
video, it looked like you were checking your operating system's time
zone setting. In the OpenERP menu, choose User: Preferences, and set the
Timezone field to America/Vancouver.

What version of OpenERP are you testing? I just tested it at the 6.1.1
tag in the 6.1 branch, and it still has the problem for me.

** Description changed:

  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.
+ 1. My OpenERP user timezone is -7:00 PDT. (Set in the OpenERP user preferences.)
  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
+ Expected behaviour: the picking list should 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 UTC adjusted for the user's time zone.
  
- I am running 6.1.0 on Ubuntu 10.04.
+ I am running 6.1.1 on Ubuntu 10.04.

** Changed in: openobject-addons
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/992259

Title:
  Calculating datetime from date cause timezone issues in sales order

Status in OpenERP Addons (modules):
  New

Bug description:
  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 OpenERP user timezone is -7:00 PDT. (Set in the OpenERP user preferences.)
  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 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 UTC adjusted for the user's time zone.

  I am running 6.1.1 on Ubuntu 10.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/992259/+subscriptions