Daily updates from Odoo
Sunday, May 10, 2026
6 changes · saas-19.3
Resolved issues and error corrections
This update fixes an issue where tax reports for GSTR2B in Russia displayed incorrect amounts due to a problem with how tax tags were applied to negative repartition lines. Now, bills are shown with positive amounts, and credit notes with negative amounts, ensuring accurate tax reporting.
Original PR description
In reverse charge taxes, tax tags are added on negative repartition lines, causing the amounts to appear with the opposite sign in reports. Due to this, credit notes were shown as positive amounts and bills as negative amounts. This commit fixes the sign handling so that: - bills are shown with positive amounts - credit notes are shown with negative amounts Forward-Port-Of: odoo/enterprise#116828 Forward-Port-Of: odoo/enterprise#116740
This update fixes a reporting issue related to Goods and Services Tax (GST) filings in India (GSTR-3B). Previously, reverse charge tax entries were incorrectly placed in a specific table. Now, these entries are correctly reported in the appropriate table, ensuring accurate tax reporting and compliance.
Original PR description
Previously, journal items for import of services with reverse charge tax were shown only in table 4(A)(2) and not in table 3.1(d). However, since table 3.1(d) is meant for supplies liable to reverse charge, those entries should also be reported there. With this commit, import of service reverse charge entries are now correctly included in table 3.1(d) as well. Forward-Port-Of: odoo/enterprise#116827 Forward-Port-Of: odoo/enterprise#116708
This update fixes an issue where the image cropper in the HTML editor didn't correctly apply style settings like rounded corners. Now, users will see a precise preview of how their images will look after cropping, ensuring consistent results and a better user experience. This was previously addressed and temporarily lost during a website builder update.
Original PR description
When cropping images with style option applied (e.g., circle), the cropper ignored these styles, causing a mismatch between the preview and the final rendered image.This made the issue especially noticeable for rounded styles. This commit ensures the cropper reflects the applied style, allowing users to preview the final result more accurately. This behavior was previously fixed in https://github.com/odoo/odoo/pull/197374 but was lost during the website builder refactoring (see commit https://github.com/odoo-dev/odoo/commit/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2). This change restores the expected behavior. task-6088098 Forward-Port-Of: odoo/odoo#263432 Forward-Port-Of: odoo/odoo#256966
This update corrects a flaw in how online statements are populated, ensuring users can retrieve a more complete history of transactions. Previously, the system only fetched transactions up to the last sync date, even if a user specified a starting date. Now, the system prioritizes the user-provided start date, combined with the last sync date, to accurately retrieve all relevant transactions.
Original PR description
When you want to find missing transactions, you have to put a starting date. But we don't use this starting date to find the last statement line, we only use the last sync date, which is wrong, because if the last sync date is after the starting date, the online transaction identifier will have the wrong date. It means we will only fetch the transactions from last sync date to today. This commit makes sure we take the start date first if it exists, then the last sync date. task-6197277 Forward-Port-Of: odoo/enterprise#116624
This update addresses a bug where the mobile app could unexpectedly log users out due to session rotation timing with webview requests (like attachments). The fix introduces a temporary flag to skip session rotation for specific requests, ensuring a smoother user experience. This doesn't pose a security risk as it simply adjusts rotation timing.
Original PR description
The session id rotates softly every 3 hours For some features, the mobile app sometimes does requests "outside" of the mobile app, through a webview for instance, and if the session rotation interval…
The session id rotates softly every 3 hours For some features, the mobile app sometimes does requests "outside" of the mobile app, through a webview for instance, and if the session rotation interval is reached at that moment, it rotates the session and the `set-cookie` instruction setting the new session cookie is received by the webview only, it's not propagated back to the mobile app. Then, this could lead for the user to be logged out of the mobile app if the soft automatic session rotation happens at the very unfortunate moment the request through that webview happens. For instance, the mobile app uses a webview to download attachments. If the session rotation happened during that request, the mobile app doesn't receive the `set-cookie` header and doesn't receive the new session id, leading for the user to be logged out of the mobile app. This revision aims to provide an option for the mobile app to temporary skip the session rotation for a specific request, such as the requests done through the webview during downloads. This option to be able to disable the rotation is not a security threat: If an attacker passes that header to disable the interval session rotation, he would avoid the session to be changed every 3 hours, but if he wouldn't he would still receive the new session id every 3 hours. The session rotation is for legitimate user / computer to rotate their session every 3 hours so that in case of data leak of their browser cookies, there is a chance the session cookie is already no longer valid when published on the public web. Legitimate users have no benefit using this option header to disable the rotation. Forward-Port-Of: odoo/odoo#263456 Forward-Port-Of: odoo/odoo#263325
This update enhances the logging process during cloud storage migration, providing more detailed information about the progress and any potential issues. Previously, migration logs were limited, making it harder to track and troubleshoot problems. Now, the logs will offer greater clarity, allowing our support team to quickly identify and resolve migration challenges for our customers.
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 Forward-Port-Of: odoo/odoo#263669 Forward-Port-Of: odoo/odoo#263557