openerp-india team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

Hello Stuart,

Yes, we have used a UTC format at server side for timezone. 
I have checked your bug report as well as patch, We understand it but we can not produce it. So it can not be accepted.

That's why  please provide appropriate steps to produce it.

Thanks and waiting for your reply!

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

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

Title:
  OpenERP 6.1rc1 emits working hours as local

Status in OpenERP Addons (modules):
  Incomplete

Bug description:
  When OpenERP generates resources for import into faces for resource
  levelling, it emits the times as local time, while emitting and
  interpreting UTC times for the task start and end dates.  This leads
  to funny offsets in the resultant data.

  Attached are two patches:

  0002-resource-Convert-working-hours-to-UTC.patch is a rewrite of
  resource.resource.calculate_working_calendar, which is time-zone
  aware.

  In doing this, I discovered that Faces does _not_ like working hours
  that span midnight.  (Our working hours are 0900-1700, and our local
  time zone is UTC+10, leading to working ours of 2300-0700 UTC.)  Thus,
  I have attached a second patch: 0001-faces-Fix-24-hour-and-end-at-
  midnight-timespans.patch which corrects this behaviour.

  The patch to faces has been submitted upstream:
  https://sourceforge.net/tracker/?func=detail&aid=3487769&group_id=155221&atid=794937

  Known issues:
  - It assumes the user's local time zone, not the time zone of the resource
  - It may break slightly where daylight savings time is involved.

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