Monday, September 5, 2016
2 changes · master
Resolved issues and error corrections
Timesheet entries now include the employee's related account so labor costs are recorded correctly for analytic entries and reinvoicing. This helps ensure employee costs flow through accurately when timesheets are used for billing.
Original PR description
TASK:https://www.odoo.com/web#id=28372&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720 … timesheets When we create a timesheet activity, it create an analytic line that allows to re-invoice the costs from the employee. If the account_id is not set on the analytic account line, the employee cost is not passed correctly on the Analytic Entries, which is not the behavior we should expect. This commit simply adds a account_id on the employee and this account is returned with the cost and the uom by the method `_get_timesheet_cost`
Excel exports now leave cells blank when a linked record field has no value, instead of showing a confusing 0. This makes exported spreadsheets easier to read and reduces the chance of users misinterpreting empty data as a real value.
Original PR description
## Description of the issue/feature this PR addresses: Improve standard Excel export readability for many2one fields: replace meaningless "0" by "" ## Current behavior before PR: With standard Excel export including m2o, you get an '0' in each cell where m2o returns no value. Then if you have a lot of m2o in your export, '0' values is the first thing you see, it makes the export difficult to read and wrong. ## Desired behavior after PR is merged: When m2o return False, we should have no value in the cell. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr