openerp-india team mailing list archive

[Bill Ennals <bennals@xxxxxxxxxxx>]

I thought that the fix for the following bug:

https://bugs.launchpad.net/openobject-addons/+bug/1204224

might have fixed this bug but unfortunately it doesn't seem to so
timesheets are still broken for large parts of the world :(

Bill.

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

Title:
  Attendance timestamp uses UTC rather than timezone

Status in OpenERP Addons (modules):
  Confirmed

Bug description:
  Even though this bug report (https://bugs.launchpad.net/openobject-
  addons/+bug/943091) seemed to indicate this particular bug occurred in
  6.1 and was fixed in 7.0, I still get the same problem.

  My timezone is Brisbane, Australia (-10 UTC).  If I sign in, either by
  using the sign in button or manually creating a sign in event in
  HR/Attendances, the browser will (mostly) display the time correctly
  for my timezone but it seems that OpenERP converts that time to UTC
  time for it's internal operations.

  Consequently, if I sign in at 8am on the first day of the timesheet
  period, OpenERP actually thinks that I've signed in at 10pm the
  previous day, which is effectively in the previous timesheet period.
  This means that when I try to submit the timesheet for validation I
  get an error saying "The timesheet cannot be validated as it does not
  contain an equal number of sign ins and sign outs".

  This is using the latest nightly build (20130513-231009).  I've tried
  with both Firefox and Safari browsers and the result is the same.

  I've included a screenshot showing that there is a discrepancy in how
  the time is recorded.  Note the difference between the time displayed
  in the form and that shown in the data above.

  Thanks,

  Bill.

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