Daily updates from Odoo
Saturday, June 27, 2026
5 changes · saas-19.3
Resolved issues and error corrections
This change fixes an access issue that could block database users from synchronizing their databases. It ensures the correct permission check is applied so the process completes without unnecessary errors.
Original PR description
The aim of this commit is to allow the databases_user to synchronize their databases. Context: The commit https://github.com/odoo/odoo/commit/846eb51a02baaf2e4f6e6780f8d0ceb23322c38b introduced a change of behavior in stable that performs some more check on access rights. Before this commit: The checks introduced by the commit resulted in an access error. There wasn't any groups on the action itself resulting in a check of the access right "write" on the model. As the model is `project.project` and a databases_user might not be granted write access on the project itself, it resulted in an access error. After this commit: The flow continues smoothly. As the action has now a group set on it, this is checked first and match the proper access right. opw-6329058 Forward-Port-Of: odoo/enterprise#121589
This update prevents a traceback that could appear when users open a billing target in Timesheets. It ensures the required leave information is available so the screen opens correctly and the billing rate indicators continue to work as expected.
Original PR description
Prerequisites to reproduce: - Enable `Billing Rate Indicators` in timesheets. - Change timesheet access of user to `User: all timesheets` - Remove Employee access Steps to Reproduce: - In Timesheets app, from configuration go to `Billing Time Targets` - Click on view button on any row Issue: - A traceback breaking the flow. Reason: - We use `hr_presence_status` widget which requires `leave_date_to` and `current_leave_id` field, change made from odoo/odoo@0496ed1 and https://github.com/odoo/odoo/commit/4b5089694436aa00254666e10cd2106b21adfe2b - Thus unavailability of field causing the traceback. Fix: - Add a related field for leave_date_to from which we get the value. Forward-Port-Of: odoo/enterprise#121888 Forward-Port-Of: odoo/enterprise#121571
This update makes sure amounts sent to Cashmatic payment machines are always calculated using a fixed 100-cent unit. It prevents mismatches with currencies that do not follow the machine’s expected decimal handling, helping payments be processed correctly.
Original PR description
Despite its API description, the Cashmatic machine always operates with 2 decimal places regardless of the currency. According to the Cashmatic head developer, only 2-decimal currencies are supported, with the sole exception of Chilean Peso (CLP) which has no decimals but is still handled with a fixed 100 cents-per-unit factor. Replace `Math.pow(10, currency.decimal_places)` with a `CENTS_PER_UNIT` constant set to 100 to make this assumption explicit. 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#272465
This update makes the website carousel walkthrough more dependable by using a clearer, deterministic way to confirm the slide URL. It helps prevent occasional test failures, which improves the reliability of website-related checks.
Original PR description
Make the step deterministic by committing the URL with edit and pressing Tab in the input instead of relying on a dropdown click. runbot-241089 Forward-Port-Of: odoo/odoo#272374
Subscription reports now exclude non-recurring products when calculating recurring revenue totals such as MRR and YRR. This prevents inflated figures if someone removes the default recurring filter in the reporting view.
Original PR description
While investigating a support ticket, we noticed that in subscription reports, recurring revenue values (MRR and YRR) are implicitly calculated for non-recurring products. This doesn't cause a direct problem when using the default search domains applied in Subscription > Reporting > Subscription > Pivot view, because a "Recurring" filter is pre-applied. But if the end user removes said filter, they might accidentally fudge the MRR and YRR numbers because the non-recurring products will contributed to the relevant grouping sums. We fix this by adding a CASE clause to explicitly ignore non-recurring products when calculating the report field for MRR and YRR , i.e. only consider `t.recurring_invoice = TRUE`. OPW-6315091 Forward-Port-Of: odoo/enterprise#121566