Hi Yannick, I just installed the latest nightly stable release which I presume should have the fix for this bug but unfortunately my bug (linked above) still exists, so either it's not related to this bug or I've done something wrong that's causing it. I've attached screenshots showing the persistent problem where the attendance record is time stamped with UTC+0 time rather than UTC-10 (Brisbane Australia) which seems to lead to a sign in at the start of the timesheet week being allocated to the previous timesheet week and the resultant error that the timesheet does not contain and even number of sign ins and sign outs.
I wait in hope I guess... Bill ** Attachment added: "Screen shot 2013-10-31 at 10.42.28 AM.png" https://bugs.launchpad.net/openobject-addons/+bug/1204224/+attachment/3896149/+files/Screen%20shot%202013-10-31%20at%2010.42.28%20AM.png -- 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/1204224 Title: [7.0] hr_timesheet_sheet - timesheet start and end are without timezone as it is date instead of datetime Status in OpenERP Community Backports (Addons): Fix Released Status in OpenERP Community Backports (Addons) 7.0 series: Fix Released Status in OpenERP Addons (modules): Confirmed Bug description: When entering attendances you might encounter serious issue as depending on the timezone, the attendances won't go on the correct timesheet. This is due because a timesheet has its start and end date defined in as DATE format. Thus it will mean timesheet start and end have no timezone defined. On the other hand, attendances will be in user timezone. This lead to attendances which will be out of scope of their timesheet if the timesheet was in local timezone too. Now let's say that a DATE in database means the timesheet is in users' timezone. Because a date isn't precise to be converted without overlapping from UTC to local timezone. And because it doesn't make sens for an Australian business to have its timesheets in UTC. Then we need to match attendances to this local timezone when trying to match the sheet_id on attendance. And as we have no timezone field defined on timesheet what we can do is taking this information from the employee. See linked MP To manage notifications about this bug go to: https://bugs.launchpad.net/ocb-addons/+bug/1204224/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~openerp-india Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-india More help : https://help.launchpad.net/ListHelp
