Monday, March 2, 2020
22 changes · master
Enhancements to existing features
The project overview now avoids showing negative timesheet hours as full-width bars in the 'time by people' section. This prevents misleading visuals where employees with negative hours appeared to have logged as much time as others.
Original PR description
colored bars representing negative hours are no more displayed in the colored bar area. if the total amount of hours is negative, nothing is displayed (bar width clamped to 0) instead of displaying a full-width grey bar (default progress bar color with a negative width). -- I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](www.odoo.com/submit-pr)
This update adds automated checks to confirm that events are correctly recognized as ongoing and can be found with the related filter. It helps reduce the risk of date-status mistakes in event management without changing how users work.
Original PR description
Adds some python tests for the is_ongoing field and search filter. LINKS Task ID : 2190611 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now turn records on or off directly from the form view without first switching into edit mode. This makes managing active and inactive records quicker and reduces unnecessary steps for everyday users.
Original PR description
Purpose Currently, to activate/deactivate records with the 'active' checkbox of their form view, the user has to switch to edit mode first. The goal of this task is to allow the user to activate/deactivate records from the readonly version of the form view. In the form view, we set widget = 'boolean_toggle' on the 'active' field in form. LINKS PR: #8918 TaskID : 2206794
Field service task validation now skips creating a sales order when there are no invoiceable products or no timesheet entries. This keeps sales records cleaner and avoids extra administrative work for tasks that should not generate billing documents.
Original PR description
Do not create a SO when validating a FSM task if there are no products to invoice or no timesheet. TaskID: 2203373
Resolved issues and error corrections
This update fixes minor spelling and hyphenation mistakes in user-facing text, including wording around bank statement imports and comma-separated values. The change improves clarity and polish without altering any business process or feature behavior.
Original PR description
- small mistake when you want to import a bank statement file: it is written: SEPA recommanded Cash Management format (CAMT.053) while it should be: recommended - comma separated -> comma-separated Task : 2200054 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Before this commit, the last cash balance was shown on the kanban card even if the cash control feature was not activated. Without this feature, the field is irrelevant. This commit hides the field when the cash control is not activated. OPW-2179888 Forward-Port-Of: odoo/odoo#44547
Original PR description
Before this commit, the last cash balance was shown on the kanban card even if the cash control feature was not activated. Without this feature, the field is irrelevant. This commit hides the field when the cash control is not activated. OPW-2179888 Forward-Port-Of: odoo/odoo#44547
This update fixes minor spelling and wording issues shown during bank statement import setup. It improves clarity for users by correcting “recommended” and hyphenating “comma-separated” in import-related text.
Original PR description
- small mistake when you want to import a bank statement file: it is written: SEPA recommanded Cash Management format (CAMT.053) while it should be: recommended - comma separated -> comma-separated Task : 2200054
This update fixes invoice extraction setup to use the current invoice field name. It helps prevent configuration issues after the field was renamed, keeping automated invoice processing working as expected.
Original PR description
=>'type' field renamed as 'move_type' task - 2168313
We use a library to get mac address of IoT in `hw_posbox_homepage`, `PrinterDriver` and `hw_escpos`. However we already have a function that does this in the helper in `hw_drivers` Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46418
Original PR description
We use a library to get mac address of IoT in `hw_posbox_homepage`, `PrinterDriver` and `hw_escpos`. However we already have a function that does this in the helper in `hw_drivers` Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46418
Before this commit, the company specific colors and font that are used to issue a report made the assets bundle recompute each time Besides, the design of the bundle forbid to make company specific asset This commit allows to not mess with assets bundle and cache while providing a way to make company specific style Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and
Original PR description
Before this commit, the company specific colors and font that are used to issue a report made the assets bundle recompute each time Besides, the design of the bundle forbid to make company specific asset This commit allows to not mess with assets bundle and cache while providing a way to make company specific style Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46598 Forward-Port-Of: odoo/odoo#44393
From saas-13.1 country_id is removed from tax.report.line and report_id are introduced from https://github.com/odoo/odoo/commit/ef0488ef91161eba5267ea29fa5c6b379c483f29 this commit. So change accordingly in this commit -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46494
Original PR description
From saas-13.1 country_id is removed from tax.report.line and report_id are introduced from https://github.com/odoo/odoo/commit/ef0488ef91161eba5267ea29fa5c6b379c483f29 this commit. So change accordingly in this commit -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46494
Finetuning of #46133 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46652
Original PR description
Finetuning of #46133 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46652
**Steps to reproduce:** * Create a subcontractor. * Create a BoM of type Subcontracting and assign the subcontractor. * Create a children contact for the subcontractor. * Creat a purchase order (or a receipt picking) with the children contact of the subcontractor. * Confirm the document. **Current behavior:** Subcontractor documents are not created. **Expected result:** They should be created. **Cause:** The BoM search is not including possible parents of the partners.
Original PR description
**Steps to reproduce:** * Create a subcontractor. * Create a BoM of type Subcontracting and assign the subcontractor. * Create a children contact for the subcontractor. * Creat a purchase order (or a receipt picking) with the children contact of the subcontractor. * Confirm the document. **Current behavior:** Subcontractor documents are not created. **Expected result:** They should be created. **Cause:** The BoM search is not including possible parents of the partners. **Solution:** With the use of `parent_of` operator in the search, we cover both cases of the children and the parent as initiators of the subcontracting. @Tecnativa Forward-Port-Of: odoo/odoo#46639
The current "mutli-company filter" of lunch product reports is hardcoded in the SQL view, based on the user's company, ignoring the general mechanism of multi company rules (env allowed companies). Task 2202678 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46253
Original PR description
The current "mutli-company filter" of lunch product reports is hardcoded in the SQL view, based on the user's company, ignoring the general mechanism of multi company rules (env allowed companies). Task 2202678 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46253
fixed the rapport from 13.0: - country_id removed from line - account.tax.report added with name and country_id - parent add to all lines task-2073735 closed-40937 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46597
Original PR description
fixed the rapport from 13.0: - country_id removed from line - account.tax.report added with name and country_id - parent add to all lines task-2073735 closed-40937 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#46597
Car model show always 0.0 car atn it reflects during the contract signature This is because the atn computation method return 0 if the current record is not link to a belgian company. The computation of the default ATN provide no record on the car model but we want to see the ATN at least when we are as main company in a belgian company Forward-Port-Of: odoo/enterprise#8859
Original PR description
Car model show always 0.0 car atn it reflects during the contract signature This is because the atn computation method return 0 if the current record is not link to a belgian company. The computation of the default ATN provide no record on the car model but we want to see the ATN at least when we are as main company in a belgian company Forward-Port-Of: odoo/enterprise#8859
When an employee sign his new contract and select a new car the value of car_id is set to the default value which is the first car available in the pool This value seems random and is not used anyway It's better to just set the value to False It will be set properly at the second signature Forward-Port-Of: odoo/enterprise#8937
Original PR description
When an employee sign his new contract and select a new car the value of car_id is set to the default value which is the first car available in the pool This value seems random and is not used anyway It's better to just set the value to False It will be set properly at the second signature Forward-Port-Of: odoo/enterprise#8937
Let's say pack1 contains 10 product1 If a move of 10 product1 is created, it is fully assigned and the package_id and result_package_id are already set to pack1. Scanning pack1 in the client action will only set the qty_done. If a move of 1 is made, it is fully assigned but only the package_id is set, not the result_package_id one since the package won't be entirely moved to the destination location. As we always try to move the entire package when scanning the pack, we have to set r
Original PR description
Let's say pack1 contains 10 product1 If a move of 10 product1 is created, it is fully assigned and the package_id and result_package_id are already set to pack1. Scanning pack1 in the client action will only set the qty_done. If a move of 1 is made, it is fully assigned but only the package_id is set, not the result_package_id one since the package won't be entirely moved to the destination location. As we always try to move the entire package when scanning the pack, we have to set result_package_id else validating the move will took all product1 out of pack1. opw-2205325 Forward-Port-Of: odoo/enterprise#8868
Tax name is created with a rounded 3 digits decimal accuracy while the tax amount have 4 digits precision. This can result with 2 different tax amounts (only last digit) pointing to the same tax name which will create a duplicate. opw-2202063 Forward-Port-Of: odoo/enterprise#8893
Original PR description
Tax name is created with a rounded 3 digits decimal accuracy while the tax amount have 4 digits precision. This can result with 2 different tax amounts (only last digit) pointing to the same tax name which will create a duplicate. opw-2202063 Forward-Port-Of: odoo/enterprise#8893
Without that, current year earnings wasn't computed properly, and the line did not match the profit and loss. Forward-Port-Of: odoo/enterprise#8769 Forward-Port-Of: odoo/enterprise#8659
Original PR description
Without that, current year earnings wasn't computed properly, and the line did not match the profit and loss. Forward-Port-Of: odoo/enterprise#8769 Forward-Port-Of: odoo/enterprise#8659
The default value was not translated. Match the weird spaces to benefit from an existing translation. Remove badly named .pot file Forward-Port-Of: odoo/enterprise#8906 Forward-Port-Of: odoo/enterprise#8866
Original PR description
The default value was not translated. Match the weird spaces to benefit from an existing translation. Remove badly named .pot file Forward-Port-Of: odoo/enterprise#8906 Forward-Port-Of: odoo/enterprise#8866
Forward-Port-Of: odoo/enterprise#8900
Original PR description
Forward-Port-Of: odoo/enterprise#8900