Daily updates from Odoo
Navigate
Branch
Wednesday, November 27, 2019
32 changes
New functionality added to Odoo
A new dashboard has been added to the Fleet app to give users a clearer overview of vehicle-related information. This helps fleet managers monitor key fleet data more easily and make faster operational decisions.
Enhancements to existing features
The employee public form now includes a hidden header area that other HR apps can use to add buttons when needed. This makes it easier to extend the employee view without changing the base screen, and it remains invisible when no buttons are added.
Original PR description
Some modules might want to add buttons in the form header of the employee public (e.g. hr_appraisal). This commit adds an empty header to easily allow view inheritance. Note: this empty header is not displayed if no buttons are indide. Task 2028794 PR odoo/enterprise#6495 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The appraisal request flow is now simpler and more flexible, allowing managers and appraisal users to request reviews from employee records with clearer follow-up actions. Notifications now respect each recipient's Odoo communication preferences, and required recipients help prevent incomplete requests.
Original PR description
This PR mainly improves the flow and usability of the "request appraisal" wizard. See commit messages for details Task 2028794 PR #6495
Resolved issues and error corrections
Corrects how a stock lot attribute is saved so inventory tracking data is stored as intended. This helps prevent incorrect behavior or missing values in stock operations that rely on lot information.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes an unnecessary dynamic filtering pattern from the base company setup and uses an existing simpler matching approach instead. It reduces maintenance complexity while keeping the expected behavior unchanged for users.
Original PR description
Start of the Dynamic Domain Removal effort. Task 2115472
This change removes an unnecessary automatic filter behavior in CRM lead handling. It helps avoid unwanted restrictions when users edit lead information, making CRM data entry more predictable.
Original PR description
Task 2115472
The website editor now correctly recognizes custom text and background colors after a recent color picker change caused some colors to be missed. This helps users keep existing styling choices visible and editable when working on website content.
Original PR description
This was broken during the recent colorpicker refactoring.
This fix corrects an internal field setting that was using the wrong attribute in affected Odoo modules. It helps ensure information is stored and handled as intended, reducing the risk of inconsistent behavior for users.
The reconciliation screen no longer suggests invoices that have a zero balance. This avoids confusing users with items that do not need to be reconciled and keeps the matching process focused on actionable payments.
Original PR description
- Create an invoice with total = 0, validate - Open the Statement Reconciliation widget - Change one of the partner to the partner set on the zero invoice The invoice appears as a suggestion, although there is no reason to reconcile it. opw-2125957
Features or functions removed from Odoo
This update removes leftover dynamic filtering rules in Sales Management because the equivalent fixed rules were already in place. It reduces duplicate configuration logic and helps keep sales order and quotation template behavior consistent.
Original PR description
Task 2115472 Not sure where I put the static domain?
This change removes a dynamic filtering rule in the Argentina localization for accounting journals. It helps simplify the setup and reduce complexity, with minimal expected impact on day-to-day business workflows.
Original PR description
Task 2115472
Miscellaneous changes
### Description of the issue/feature this PR addresses: We need to be able to create a bank accounts of type cbu for EDI validation of mipyme invoices. ### Current behavior before PR: In saas version stdnum library is < 1.11 so the functionality to validate the cbu is not defined, which lead to not be able to create bank accounts of type cbu. ### Desired behavior after PR is merged: If available in the environment use the stdnum.ar.cbu.validate, if not use our own validate method
Original PR description
### Description of the issue/feature this PR addresses: We need to be able to create a bank accounts of type cbu for EDI validation of mipyme invoices. ### Current behavior before PR: In saas version stdnum library is < 1.11 so the functionality to validate the cbu is not defined, which lead to not be able to create bank accounts of type cbu. ### Desired behavior after PR is merged: If available in the environment use the stdnum.ar.cbu.validate, if not use our own validate method that validate the cbu in order to be able to create bank accounts of type cbu. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40632
Forward-Port-Of: odoo/odoo#40965
Original PR description
Forward-Port-Of: odoo/odoo#40965
Updating the quantity to produce in a production order will recompute each raw move's unit factor. The issue was this computation did not take care of the previously product quantity. The unit factor was wrong and so the next created workorder lines get the wrong quantity. Example: - 1 components for 1 finished product (unit_factor = 1) - Create a production for 2 finished product -> quantity to consume = 2 - Produce 1 then change quantity to produce to 3 -> quantity to consume =
Original PR description
Updating the quantity to produce in a production order will recompute
each raw move's unit factor. The issue was this computation did not
take care of the previously product quantity. The unit factor was wrong
and so the next created workorder lines get the wrong quantity.
Example:
- 1 components for 1 finished product (unit_factor = 1)
- Create a production for 2 finished product -> quantity to consume = 2
- Produce 1 then change quantity to produce to 3 -> quantity to consume = 3
and quantity done = 1 but unit factor became 1.5
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#40932
Forward-Port-Of: odoo/odoo#40484-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40201
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40201
Forward-Port-Of: odoo/odoo#39863
Original PR description
Forward-Port-Of: odoo/odoo#39863
The status ticket contains ESC/POS commands but was printed on all printers connected in USB. Plugging a printer that doesn't support ESC/POS resulted in undefined behaviors. We now only print this status ticket on ESC/POS printers. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40923
Original PR description
The status ticket contains ESC/POS commands but was printed on all printers connected in USB. Plugging a printer that doesn't support ESC/POS resulted in undefined behaviors. We now only print this status ticket on ESC/POS printers. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40923
task: https://www.odoo.com/web#id=2048024&action=327&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.4c45aaf794a5761cacd37e195ada7f12 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39689
Original PR description
task: https://www.odoo.com/web#id=2048024&action=327&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.4c45aaf794a5761cacd37e195ada7f12 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39689
The use of an emulator (qemu) for the IoT Box build posed compatibility and performance issues. So we have the Raspbian filesystem to install and configure packages. Task: 2145445 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#40839
Original PR description
The use of an emulator (qemu) for the IoT Box build posed compatibility and performance issues. So we have the Raspbian filesystem to install and configure packages. Task: 2145445 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#40839
Description of the issue/feature this PR addresses: detailed issue here: https://github.com/odoo/odoo/issues/39406 Current behavior before PR: error 500 when process order Access field Error Desired behavior after PR is merged: Complete validate order when customer paid with paypal method -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39408
Original PR description
Description of the issue/feature this PR addresses: detailed issue here: https://github.com/odoo/odoo/issues/39406 Current behavior before PR: error 500 when process order Access field Error Desired behavior after PR is merged: Complete validate order when customer paid with paypal method -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#39408
- Handle the notifications in Odoo - On any object, e.g. a SO, user A a note and ping user B - As user B, go to Discuss and reply to the note The reply is sent a regular message. Actually, everything is available to reply with the right message type in: https://github.com/odoo/odoo/blob/bae8ab7d93143e082e1d1a9cbe20a350c2d34d07/addons/mail/static/src/js/discuss.js#L1327 It is simply unset. opw-2088619 Description of the issue/feature this PR addresses: Current behavior bef
Original PR description
- Handle the notifications in Odoo - On any object, e.g. a SO, user A a note and ping user B - As user B, go to Discuss and reply to the note The reply is sent a regular message. Actually, everything is available to reply with the right message type in: https://github.com/odoo/odoo/blob/bae8ab7d93143e082e1d1a9cbe20a350c2d34d07/addons/mail/static/src/js/discuss.js#L1327 It is simply unset. opw-2088619 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#40882 Forward-Port-Of: odoo/odoo#40863
Reproduce the issue - Install CRM & sale_crm - Create an opportunity - Create a quotation from the opportunity The name of the draft is the opportunity's name instead of "New" - Add a "Storage Box" to the quotation, for instance - Confirm the quotation - Check the delivery note The name of the delivery note is the opportunity's name instead of WH/OUT/... Cause This issue is caused by 4c9c249c. It seems that we pass an extra defa
Original PR description
Reproduce the issue
- Install CRM & sale_crm
- Create an opportunity
- Create a quotation from the opportunity
The name of the draft is the opportunity's name instead of "New"
- Add a "Storage Box" to the quotation, for instance
- Confirm the quotation
- Check the delivery note
The name of the delivery note is the opportunity's name instead of
WH/OUT/...
Cause
This issue is caused by 4c9c249c. It seems that we pass an extra
default_name in the context.
This commit removes the extra default_name from the context.
OPW-2122928
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#40671@rco-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40913 Forward-Port-Of: odoo/odoo#39693
Original PR description
@rco-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40913 Forward-Port-Of: odoo/odoo#39693
As the group_account_invoice doesn't have the access rights to unlink the account.partial.reconcile/account.full.reconcile, there was impossible for the user to undo a reconciliation. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40890 Forward-Port-Of: odoo/odoo#40845
Original PR description
As the group_account_invoice doesn't have the access rights to unlink the account.partial.reconcile/account.full.reconcile, there was impossible for the user to undo a reconciliation. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40890 Forward-Port-Of: odoo/odoo#40845
- Activate product packing - Create a PO for a stockable product, validate - In the barcode interface, go to the created picking - Set the product quantity - Click on 'Put in Pack' An error is raised: 'All the products currently reserved in the picking are already in a pack...' In the regular interface, the procedure is to create the move lines manually, therefore setting a quantity done. However, this is not possible in the barcode, and `move_line_nosuggest_ids` is always empty.
Original PR description
- Activate product packing - Create a PO for a stockable product, validate - In the barcode interface, go to the created picking - Set the product quantity - Click on 'Put in Pack' An error is raised: 'All the products currently reserved in the picking are already in a pack...' In the regular interface, the procedure is to create the move lines manually, therefore setting a quantity done. However, this is not possible in the barcode, and `move_line_nosuggest_ids` is always empty. We introduce a special use case to bypass this in the case of the barcode view. opw-2127637 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#40920
opw 2144639 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#40874
Original PR description
opw 2144639 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#40874
fixes #38014 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40838
Original PR description
fixes #38014 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#40838
In most use case, when we edit the website we have a situation such as: ``` <div id="wrap" branding-attributes="..."> <section class="mycontent">hi!</section> </div> ``` When we modify a part, we replace all child nodes of the branded element. But if we had more complex content such as: ``` <div id="wrap"> <section class="mycontent" branding-attributes="...">ho!</section> <t t-call-assets="web.assets_common" t-js="false" t-css="false"/> </div> ``` we have a t-call inside the div
Original PR description
In most use case, when we edit the website we have a situation such as:
```
<div id="wrap" branding-attributes="...">
<section class="mycontent">hi!</section>
</div>
```
When we modify a part, we replace all child nodes of the branded
element.
But if we had more complex content such as:
```
<div id="wrap">
<section class="mycontent" branding-attributes="...">ho!</section>
<t t-call-assets="web.assets_common" t-js="false" t-css="false"/>
</div>
```
we have a t-call inside the div#wrap, so branding is distributed to
child that could have attribute modified (eg. changing background).
Then if `<section/>` node is saved, the possibly modified attributes
are lost.
opw-2122947
Forward-Port-Of: odoo/odoo#40782
Forward-Port-Of: odoo/odoo#40345The current 'Newly Hired' filter is incorrect in several ways: - the compute method doesn't assign the value correctly - the search method mixes `hr.applicant` IDs with `hr.employee` IDs Moreover, it relies on the fact that the job position is opened. Some positions might always be opened, so the result is inaccurate. We make the simpler assumption that the newly hired people are employees created less than 120 days ago. opw-2125861 Description of the issue/feature this PR addres
Original PR description
The current 'Newly Hired' filter is incorrect in several ways: - the compute method doesn't assign the value correctly - the search method mixes `hr.applicant` IDs with `hr.employee` IDs Moreover, it relies on the fact that the job position is opened. Some positions might always be opened, so the result is inaccurate. We make the simpler assumption that the newly hired people are employees created less than 120 days ago. opw-2125861 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#40841
- Create an invoice with total = 0, validate - Open the Statement Reconciliation widget - Change one of the partner to the partner set on the zero invoice The invoice appears as a suggestion, although there is no reason to reconcile it. opw-2125957 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:
Original PR description
- Create an invoice with total = 0, validate - Open the Statement Reconciliation widget - Change one of the partner to the partner set on the zero invoice The invoice appears as a suggestion, although there is no reason to reconcile it. opw-2125957 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#40712
- Activate product packing - Create a PO for a stockable product, validate - In the barcode interface, go to the created picking - Set the product quantity - Click on 'Put in Pack' An error is raised: 'All the products currently reserved in the picking are already in a pack...' In the regular interface, the procedure is to create the move lines manually, therefore setting a quantity done. However, this is not possible in the barcode, and `move_line_nosuggest_ids` is always empty.
Original PR description
- Activate product packing - Create a PO for a stockable product, validate - In the barcode interface, go to the created picking - Set the product quantity - Click on 'Put in Pack' An error is raised: 'All the products currently reserved in the picking are already in a pack...' In the regular interface, the procedure is to create the move lines manually, therefore setting a quantity done. However, this is not possible in the barcode, and `move_line_nosuggest_ids` is always empty. We introduce a special use case to bypass this in the case of the barcode view. opw-2127637 Forward-Port-Of: odoo/enterprise#6901
Have the same behavior as other stat button that open the calendar view and highlight the related events but still show other meetings. opw-2131494 Forward-Port-Of: odoo/enterprise#6897 Forward-Port-Of: odoo/enterprise#6869
Original PR description
Have the same behavior as other stat button that open the calendar view and highlight the related events but still show other meetings. opw-2131494 Forward-Port-Of: odoo/enterprise#6897 Forward-Port-Of: odoo/enterprise#6869