openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <943091@xxxxxxxxxxxxxxxxxx>]

You're definitely right, hr_timesheet_sheet uses a series of date (not
datetime!) fields  that need to be properly computed using client time
instead of server time (UTC), using the same technique and for the same
reasons explained on bug 925361.

Thanks for reporting and providing the very informative screenshot in
comment #4!

** Project changed: openerp-web => openobject-addons

** Changed in: openobject-addons
   Importance: Undecided => Medium

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

** Changed in: openobject-addons
     Assignee: (unassigned) => OpenERP R&D Addons Team 3 (openerp-dev-addons3)

** Changed in: openobject-addons
    Milestone: None => 6.1

-- 
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/943091

Title:
  More time-zone issues

Status in OpenERP Addons (modules):
  Confirmed

Bug description:
  In a similar vein as https://bugs.launchpad.net/openerp-
  web/+bug/918257, hr_timesheet_sheet displays "Today" as UTC, rather
  than the local. When manually signing in or out, the attendance is
  pushed to the UTC day. This is very confusing.

  If I understand correctly, datetime is set to UTC in the server. In
  hr_timesheet_sheet_view.xml, <field name="date_current" nolabel="1"/>
  will always be UTC, which is not what I expect. This completely screws
  up the daily attendance as I sign in on one day and sign out on the
  next day.

  What would be the recommended best practice to fix this?

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