Daily updates from Odoo
Sunday, March 29, 2026
17 changes
5 changes
Resolved issues and error corrections
This change removes a duplicate field in the customer rating form. The issue stemmed from a dependency conflict between the Helpdesk and Portal Rating modules. This fix ensures a cleaner and more streamlined user experience for customers submitting ratings.
Original PR description
This reverts commit de8dd6703393ec83fbdbe76dd0c69654ac72e662 because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of helpdesk module. task-5359052 Forward-Port-Of: odoo/enterprise#112422
This update removes a duplicate 'Comment' field from the customer rating form. The field was unintentionally created due to a dependency issue between the 'project' module and the 'portal_rating' module. This change ensures a cleaner and more streamlined user experience for customers submitting ratings.
Original PR description
This reverts commit 1f762031d8afdb0dcf019205c3b60bba6ab8279c because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of project module. task-5359052 Forward-Port-Of: odoo/odoo#256527
This update resolves a problem where creating expense payments for Branch companies resulted in an error because the payment was incorrectly linked to the parent company's journal entries. The fix ensures that payment journal entries are correctly associated with the expense company, preventing these errors and improving the accuracy of expense reporting for Branch operations.
Original PR description
**Steps to reproduce:** - Install Accounting and Expenses - Create a Branch company (e.g. Branch) - In company selector, select both Branch (as main) and its parent - In Bank journal settings, make…
**Steps to reproduce:** - Install Accounting and Expenses - Create a Branch company (e.g. Branch) - In company selector, select both Branch (as main) and its parent - In Bank journal settings, make sure that there is an outstanding payment account for "Manual Payment" - Create an employee in Branch - Create an expense: * Category: [any] (e.g. [EXP_GEN] Expenses) * Total: [anything] (e.g. 100.00) * Employee: [the created employee] * Paid By: company * Company: Branch - Create Report - Submit to Manager - Approve **Issue:** A UserError is raised because it tries to create a payment in Branch linked to a journal entry in the parent company. **Cause:** The payment is initialized with the company of the expense but not the related journal entry. **(A similar issue happens with an expense paid by the employee when generating the bill upon approval of the expense sheet)** opw-6007859 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#256489 Forward-Port-Of: odoo/odoo#254434
This update resolves a mobile display issue where filters remained visible even after selecting the 'hide' option. The fix ensures that filters are only rendered in mobile view when a visibility option other than 'hide' is chosen, improving the user experience on smaller screens. This change enhances the usability of the shop page for mobile users.
Original PR description
Steps to reproduce: 1) Go to the shop page 2) Open the editor and select the 'hide' option for filters 3) Switch to mobile view and click on the 'Filters' button Issue: - Filters are still displayed in mobile view even when the 'hide' option is selected in the editor. Cause: - The attribute filters template is always rendered in mobile view without checking the selected visibility option. Fix: - Add a condition to the `t-call` of the filters template so it is only rendered when an option other than 'hide' is selected. opw-5982147 Forward-Port-Of: odoo/odoo#256213 Forward-Port-Of: odoo/odoo#255997
This update corrects a visual inconsistency in the Odoo HR attendance module. Previously, overtime ruleset titles had incorrect styling due to a misconfigured element. Removing this element ensures all form titles now match the standard Odoo styling, improving the overall user experience and visual consistency.
Original PR description
**Before this commit** The title of an overtime ruleset record was shown with the incorrect background color and width. This is because the field was mistakenly wrapped in a `<header>` element. This…
**Before this commit** The title of an overtime ruleset record was shown with the incorrect background color and width. This is because the field was mistakenly wrapped in a `<header>` element. This makes the overtime ruleset titles look inconsistent compared to other forms in Odoo. Light mode <img width="1573" height="1027" alt="Screenshot 2026-03-25 at 12 48 14 PM" src="https://github.com/user-attachments/assets/602ae625-d80d-45c3-bc01-f928ab179b7a" /> Dark mode <img width="1570" height="1025" alt="Screenshot 2026-03-25 at 12 49 03 PM" src="https://github.com/user-attachments/assets/14b3a1ee-33c0-4c3e-b66f-79d450baa6ac" /> **After this commit** We remove the `<header>` element that wraps the title so that its background and width match the expected styling for forms in Odoo. Light mode <img width="1575" height="1027" alt="Screenshot 2026-03-25 at 2 19 35 PM" src="https://github.com/user-attachments/assets/ee2dd6bd-3ab2-487c-8826-c2334f5e1258" /> Dark mode <img width="1573" height="1024" alt="Screenshot 2026-03-25 at 2 19 09 PM" src="https://github.com/user-attachments/assets/cb59bdeb-f599-4553-acc1-991bf923756d" /> opw-6069360 Forward-Port-Of: odoo/odoo#255910
5 changes
Resolved issues and error corrections
This update removes a duplicate field for comments on customer ratings forms. The original change introduced an issue because the related module wasn't properly integrated with the Helpdesk module. This reversion ensures the customer rating form functions as intended, streamlining the feedback process.
Original PR description
This reverts commit de8dd6703393ec83fbdbe76dd0c69654ac72e662 because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of helpdesk module. task-5359052 Forward-Port-Of: odoo/enterprise#112422
This update ensures that all future appraisals and related data for departing employees are automatically removed from the system. This prevents outdated appraisals from cluttering the system and ensures data accuracy when an employee leaves the company. It also removes the employee from any appraisal roles they held.
Original PR description
Currently, when an employee leaves the company, their future appraisals remain active and can still be completed. This fix ensures that, upon employee departure: - all future appraisals are removed - the employee is removed from appraisals where they are an appraiser - all their personal goals are archived task: 6036427 Forward-Port-Of: odoo/enterprise#112061 Forward-Port-Of: odoo/enterprise#111589
This update removes a duplicate 'Comment' field from the customer rating form. The field was originally defined in a separate module (portal_rating) that wasn't properly integrated with the main project module. This change ensures a cleaner and more streamlined user experience for rating submissions.
Original PR description
This reverts commit 1f762031d8afdb0dcf019205c3b60bba6ab8279c because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of project module. task-5359052 Forward-Port-Of: odoo/odoo#256527
This update resolves a problem where creating payments for expenses linked to a 'Branch' company would trigger an error. The fix ensures that payment journal entries correctly link to the expense company, preventing these errors and improving the accuracy of financial reporting for multi-company setups.
Original PR description
**Steps to reproduce:** - Install Accounting and Expenses - Create a Branch company (e.g. Branch) - In company selector, select both Branch (as main) and its parent - In Bank journal settings, make…
**Steps to reproduce:** - Install Accounting and Expenses - Create a Branch company (e.g. Branch) - In company selector, select both Branch (as main) and its parent - In Bank journal settings, make sure that there is an outstanding payment account for "Manual Payment" - Create an employee in Branch - Create an expense: * Category: [any] (e.g. [EXP_GEN] Expenses) * Total: [anything] (e.g. 100.00) * Employee: [the created employee] * Paid By: company * Company: Branch - Create Report - Submit to Manager - Approve **Issue:** A UserError is raised because it tries to create a payment in Branch linked to a journal entry in the parent company. **Cause:** The payment is initialized with the company of the expense but not the related journal entry. **(A similar issue happens with an expense paid by the employee when generating the bill upon approval of the expense sheet)** opw-6007859 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#256489 Forward-Port-Of: odoo/odoo#254434
This update fixes an issue where mixed POS orders (with both sales and settlement lines) weren't being properly validated. The change ensures that settlement lines are correctly identified, preventing incorrect validation and improving the accuracy of financial reporting for Saudi POS transactions. This update aligns with newer Odoo versions and enhances the reliability of the l10n_sa_edi_pos integration.
Original PR description
# Description of the issue/feature this PR addresses: From saas-18.3 onward, the pos_settle_due module introduced a new method to identify settlement lines. While the old method **isSettleDueLine()**…
# Description of the issue/feature this PR addresses: From saas-18.3 onward, the pos_settle_due module introduced a new method to identify settlement lines. While the old method **isSettleDueLine()** is still there, the new **isAnySettleLine()** covers both order settlement and invoice settlement. This change was not reflected in the Saudi POS EDI integration during forward-porting, which caused incorrect validation when processing POS orders containing both regular sale lines and settlement lines. # Current behavior before PR: - Orders containing a mix of new sale lines and settlement lines could bypass the intended validation. - The validation logic relied on the old isSettleDueLine() method # Desired behavior after PR is merged: - Update the validation flow to use isAnySettleLine() (when available) to correctly detect settlement lines. - Prevent validation of POS orders that contain both settlement lines and new sale lines. - Ensure compatibility with newer versions of the pos_settle_due module and restore the intended settlement validation behavior. - Test case to ensure no regression on this feature I confirm I have signed the CLA and read the PR guidelines at [www.odoo.com/submit-pr](http://www.odoo.com/submit-pr) Forward-Port-Of: odoo/odoo#256177 Forward-Port-Of: odoo/odoo#254275
1 change
Resolved issues and error corrections
This update removes a duplicate 'Comment' field from the customer rating form. The original field was unintentionally included due to a dependency issue with a separate module. This change ensures a cleaner and more streamlined user experience for customers submitting ratings.
Original PR description
This reverts commit de8dd6703393ec83fbdbe76dd0c69654ac72e662 because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of helpdesk module. task-5359052 Forward-Port-Of: odoo/enterprise#112422
1 change
Resolved issues and error corrections
This change removes a duplicate 'Comment' field from the customer rating form. The original implementation relied on a module not directly connected to the Helpdesk module, causing an issue. This reversion ensures the form functions correctly and avoids redundant data entry.
Original PR description
This reverts commit de8dd6703393ec83fbdbe76dd0c69654ac72e662 because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of helpdesk module. task-5359052
1 change
Resolved issues and error corrections
This change removes a duplicate 'Comment' field from the customer rating form. The original field was unintentionally included due to a dependency issue with a separate module. This update ensures a cleaner and more streamlined user experience for customers submitting ratings.
Original PR description
This reverts commit de8dd6703393ec83fbdbe76dd0c69654ac72e662 because the publisher_comment field in `rating.rating` model is defined in `portal_rating` module and that module is not in the dependencies of helpdesk module. task-5359052 Forward-Port-Of: odoo/enterprise#112422
1 change
Resolved issues and error corrections
This update allows for richer formatting within server action messages, specifically using 'Markup' to display bold text. Previously, messages were not formatted correctly. This change improves the clarity and presentation of messages sent through server actions, enhancing user communication.
Original PR description
Before this PR, for exemple a message post is not formated : record.message_post(body="<strong>Hello Word!</strong>")
now it is possible to use Markup in action server: record.message_post(body=Markup("<strong>Hello Word!</strong>"))
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-pr3 changes
Resolved issues and error corrections
This update resolves a security vulnerability where users with limited access could inadvertently read data from related records when using computed x2many fields with sudo access. The fix ensures that read access is properly managed, preventing unauthorized data retrieval and maintaining data security. This primarily impacts company-level data access.
Original PR description
Given a x2many field computed with `compute_sudo=True`, it is possible that the value computed value returns records that the user cannot read, which is fine because the user can only see the id of…
Given a x2many field computed with `compute_sudo=True`, it is possible that the value computed value returns records that the user cannot read, which is fine because the user can only see the id of the record an it's name, but nothing more. However, trying to read that field with the field's getter will call `convert_to_record`, which will filter the active records or not depending on the context key `active_test`, because the cache is shared between the different contexts. This is done performing a `filtered` on the records, which requires read access on the returned records. To reproduce: * Create a company branch * Create a new user with access only to that company branch * Try to read `parent_ids` of that new branch. It is particularly important to have access at least to the ids of the companies because one can have access to records belonging to the parent company without having access to the company itself (i.e. accounting accounts, journals, taxes, analytic accounts, products, ...)
Following the Odoo 17 upgrade, users experienced an inability to view products. This pull request addresses this issue by correcting a query error that was causing the problem. The fix ensures that product viewing functionality is restored, improving usability for all users.
Original PR description
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
This update ensures Odoo doesn't attempt to load missing addon paths, preventing errors and improving stability. Previously, Odoo would fail silently if an addon path wasn't found, making it difficult to identify configuration issues. Now, Odoo will refuse to start if these paths are missing, ensuring a more reliable system.
Original PR description
Description of the issue/feature this PR addresses: Before this commit, Odoo would not validate addons path when the process started, resulting in the developer being unaware of an incorrect configuration. Current behavior before PR: When the statics paths were requested in Odoo, 'os.listdir' would raise an Exception, and no static path would be loaded. Desired behavior after PR is merged: This commits validates the addons paths and forbids Odoo from running if a path does not exist. closes #181316 I have yet to sign the corporate CLA once I receive the OK.