Daily updates from Odoo
Sunday, March 29, 2026
5 changes · saas-19.1
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