Daily updates from Odoo
Monday, July 28, 2025
7 changes · master
Enhancements to existing features
A Web Studio automated test was updated to reflect a recent platform change in how field information is handled. This helps keep quality checks aligned with the product and reduces the risk of false test failures during development.
Original PR description
This commit adapts a test to the addition of the copy attribute in fields_get made in https://github.com/odoo/odoo/pull/219253 task-4920305
Added a button in the website settings that redirects to the website generator configurator. The goal is to have a standard way to import a website without necessarily it being part of the onboarding flow. closes odoo/enterprise#88334 Forward-Port-Of: odoo/enterprise#90071
Original PR description
Added a button in the website settings that redirects to the website generator configurator. The goal is to have a standard way to import a website without necessarily it being part of the onboarding flow. closes odoo/enterprise#88334 Forward-Port-Of: odoo/enterprise#90071
Online orders received through UrbanPiper now calculate and display taxes more accurately based on the restaurant’s country and fiscal setup. This helps businesses avoid tax mismatches, especially for Indian GST rules where aggregator-paid and merchant-paid taxes are handled differently.
Original PR description
**: pos_urban_piper_zomato, pos_urban_piper_swiggy After this commit: --- - For orders outside India, price are received from UrbanPiper as tax-inclusive. Odoo now properly computes the unit price and applies taxes based on the fiscal position. - For India, special handling is implemented: - 5% GST is collected and paid by the aggregator, so only this tax is added via fiscal position mapping. - For other tax rates like 12% or 18%, the merchant is responsible, so these must be configured explicitly in the fiscal position. Note: --- - If a user does **not** want to receive a particular tax in the order, they must manually add a line for it in the fiscal position. Task: 4862417 Forward-Port-Of: odoo/enterprise#91036 Forward-Port-Of: odoo/enterprise#88118
Helpdesk ticket updates made from the customer portal now show the customer as the author in the chatter instead of OdooBot. This makes ticket history clearer for support teams, while still using OdooBot when no customer is linked.
Original PR description
- When closing the ticket form portal, the customer's name appears in the chatter instead of OdooBot. - When the ticket is closed by a public user, the customer appears in the chatter. - When no customer is specified, the OdooBot will appear in the chatter. task-4809115
The editing toolbar now offers font color instead of strikethrough in compact mode, making common formatting easier to access. Knowledge article formatting options are also shown more selectively, so users only see relevant paragraph or normal text choices based on the editor context.
Original PR description
I. This PR replaces strike through with font color in compact toolbar. II. This PR replaces the baseContainer config with baseContainers, a list that defines the allowed base containers. The first element of the list now serves as the default, equivalent to the previous baseContainer. This change enables conditional display of "Normal" and "Paragraph" options in the toolbar. For example, if baseContainers only includes "DIV", only the "Normal" option will be shown. Similarly, if it only includes "P", only the "Paragraph" option will be shown. community-https://github.com/odoo/odoo/pull/216884 task-4770922
Users now see a confirmation popup when moving documents to a folder that would change who can access them. This helps prevent accidental permission changes and makes folder access implications clearer before the move is completed.
Original PR description
Purpose ======= Making sure people are aware of the access rights change when moving documents to a different folder. Specification ============= When moving documents to a target folder, add a confirmation popup specifying the target folder access rights if making the move will impact the dragged documents access rights. Task-4822908
The database expiration message now reflects the updated timing based on the next invoice date, giving customers a clearer payment window. This helps encourage earlier payments and reduces last-minute renewal risk.
Original PR description
Previously, the database expiration date was set to the same date as the expiration field, which is now defined as 15 days after the next invoice date. Issue: Users tend to wait until the last minute to pay. This improvement aims to better handle expiration timing and encourage timely payments. TaskID: 4384877 Forward-Port-Of: odoo/enterprise#90931 Forward-Port-Of: odoo/enterprise#90664