Friday, May 15, 2026
6 changes · 18.0
Resolved issues and error corrections
This update fixes an issue where refused overtime was incorrectly included in work entry calculations. Previously, the system was adding validated overtime hours, leading to inaccurate work time records. Now, refused overtime is properly excluded, ensuring accurate attendance-based work entries are generated.
Original PR description
- While fixing the bug where refused overtime in `no_validation` mode was still retaining validated overtime hours, this exposed an issue in attendance-based work entry generation. Refused overtime was being excluded using `validated_overtime_hours`. - After the previous fix, `validated_overtime_hours` becomes `0` on refusal, causing the full attendance duration to be included in generated work entries. **Example**: ``` Attendance: 13:00–20:00 Overtime: 2h Overtime status: refused Validated overtime: 0h ``` **Before**: `Generated work entry = 7h` **Expected**: `Generated work entry = 5h` ### Fix - For refused overtime, subtract `overtime_hours` from the attendance interval instead of `validated_overtime_hours`, ensuring refused overtime remains excluded from attendance-based work entries. task-5949741
This update corrects a bug where old manual bank statement entries were incorrectly suggested as matches for new transactions. The change ensures that only relevant, current manual operations are considered during automated reconciliation, improving the accuracy of bank statement matching. This prevents potential errors in financial reporting.
Original PR description
Currently, after validating a transaction with a manual operation, the aml resulting from the manual operation can still be selected and matched with other transactions. Steps to reproduce: - Create…
Currently, after validating a transaction with a manual operation, the aml resulting from the manual operation can still be selected and matched with other transactions. Steps to reproduce: - Create a transaction for 500 dollars - Create a manual counterpart line for the bank statement line with label "test123" and validate - Create another transaction of -1000 dollars and label "test123" Issue: The manual counterpart line matched before is being suggested against the new transaction. The perfect match reconciliation model will reconcile the manual counterpart line with the new bank statement line. Analysis: During the retrieval of possible aml to match we only look at the aml reconciliation state. Manual counterpart lines created during the validation of a previous statement line are still selectable candidates, causing false positive matches in automated reconciliation models. Test in Enterprise: https://github.com/odoo/enterprise/pull/115847 opw-6045050 Forward-Port-Of: odoo/odoo#262295
This update corrects a bug where previously validated manual transactions could incorrectly be matched with new transactions. The change ensures that manual counterpart lines are no longer suggested for matching with subsequent transactions, improving the accuracy of reconciliation reports. This resolves a potential issue with financial reporting.
Original PR description
Currently, after validating a transaction with a manual operation, the aml resulting from the manual operation can still be selected and matched with other transactions. Steps to reproduce: - Create a transaction for 500 dollars - Create a manual counterpart line for the bank statement line with label "test123" and validate - Create another transaction of -1000 dollars and label "test123" Issue: The manual counterpart line matched before is being suggested against the new transaction. The perfect match reconciliation model will reconcile the manual counterpart line with the new bank statement line. Adding test for community branch opw-6045050 Forward-Port-Of: odoo/enterprise#115847
This update resolves an issue where a notification badge remained visible on the 'Send to Kitchen' button after a general note was removed from the Point of Sale (POS) system. The fix normalizes empty notes to an empty string, ensuring the badge disappears correctly when a note is deleted. This improves the user experience by removing unnecessary notifications.
Original PR description
Steps to reproduce:
-----------
- Open POS Restaurant
- Add a General Note
- Remove the General Note
- The message badge on “Send to Kitchen” remains visible
Issue:
-----------
Removing a General Note set `general_note` to `undefined`, which was
detected as a change and kept the badge visible.
Fix:
--------------
Normalize empty General Notes to an empty string ("") so removing a note
restores the correct initial state.
Task-6101501
Related PR: odoo/enterprise#113514This update corrects a technical issue where archived delivery carriers were being unintentionally included in the carrier selection process. Previously, the system would pass information about inactive carriers, leading to incorrect carrier choices. This change ensures that only active carriers are used, improving data accuracy and reliability.
Original PR description
Issue: property_delivery_carrier_id on res.partner can hold an archived delivery.carrier record. Meaning that we pass an archived record to the context and that we can select the archievd delivery.carrier in the choose.delivery.carrier wizard. Solution: Only pass active records through the context. opw-6125792 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263819
Documentation and clarification updates
This pull request implements a Corporate Legal Agreement (CLA) for QoQa, ensuring compliance with Odoo's contribution guidelines. The change was backported to version 18.0 to meet QoQa's requirements. This update allows QoQa to integrate with Odoo, adhering to legal and licensing standards.
Original PR description
Description of the issue/feature this PR addresses: This is the corporate CLA for QoQa. I backported #262581 because we need it from 18.0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr