c2c-oerpscenario team mailing list archive

[James Jesudason <james.jesudason@xxxxxxxxxxxxx>]

Public bug reported:

bzr revno: 4437

There are errors in the Employees Timesheet report and the Employee
Timesheet report which prevent the reports from generating the correct
information.

The Employees Timesheet incorrectly passes the employee ID into the 'emp_create_xml' method so it is generating the timesheet for the wrong user. It should pass in the user id.
Steps to reproduce: use a database with multiple users and employees. Report on users that have their hr.employee ID different to their res.user ID.

The Employee Timesheet ignores the employee_id parameter and incorrectly uses the logged-on user's id to generate the report. So the generated report will be incorrect if the user chooses a different employee in the wizard.
Steps to reproduce: use a database with multiple users and employees. Run the report for the logged on user and then re-run for another employee. You'll see that the reports are identical, even though is different user was selected.

A patch is attached to fix both reports.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
[hr_timesheet] Employee timesheet reports confuse employee id and user id
https://bugs.launchpad.net/bugs/669533
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: New

Bug description:
bzr revno: 4437

There are errors in the Employees Timesheet report and the Employee Timesheet report which prevent the reports from generating the correct information.

The Employees Timesheet incorrectly passes the employee ID into the 'emp_create_xml' method so it is generating the timesheet for the wrong user. It should pass in the user id.
Steps to reproduce: use a database with multiple users and employees. Report on users that have their hr.employee ID different to their res.user ID.

The Employee Timesheet ignores the employee_id parameter and incorrectly uses the logged-on user's id to generate the report. So the generated report will be incorrect if the user chooses a different employee in the wizard.
Steps to reproduce: use a database with multiple users and employees. Run the report for the logged on user and then re-run for another employee. You'll see that the reports are identical, even though is different user was selected.

A patch is attached to fix both reports.