Wednesday, June 25, 2025
5 changes · saas-18.3
Resolved issues and error corrections
The custom color picker now keeps the opacity slider fully visible at the top, regardless of the selected color's transparency. This makes choosing text colors more predictable for users editing content in apps such as Knowledge.
Original PR description
Before this commit the opacity slider in the custom color picker ( introduced in this [commit]) in the custom tab would change its opacity at the top based on the opacity of the color you selected, which isn't expected behaviour. To see the issue: - go to any apps where you can edit text (for example, Knowledge) - select any text and expand the toolbar to see the colors options - click on "Apply font color" and navigate to the Custom tab - slide the opacity slider down => slider's opacity changes, this happens because its style's linear gradient goes from our colors opacity value to 0 instead of 100 to 0. [commit]: https://github.com/odoo/odoo/commit/7bbe05b34541d641dd431662e835d2a26e1adfab
The XML export option now only works for invoices that have been posted. This prevents users from encountering an error when trying to export XML from draft invoices, where required invoice details are not yet finalized.
Original PR description
Currently, an error is raised when attempting to export the XML for a draft invoice. **Steps to Reproduce:** - Install the `account_edi_ubl_cii` module. - Create an invoice with customer **OpenWood**. - Without confirming the invoice, go to `Print > Export XML`. **Error:** `AttributeError - 'bool' object has no attribute 'replace'` **Cause:** In draft state, the invoice name is `False`, leading to an `AttributeError` when calling `replace()` on bolean value. - [1] [1] - https://github.com/odoo/odoo/blob/8bc24feca01a7d0e45606ac97e45ddf442670392/addons/account_edi_ubl_cii/models/account_edi_xml_ubl_bis3.py#L32-L33 Restrict the XML export feature to only allow export for posted invoices, where the name is always defined. Sentry - 6695898207
The Calendar privacy field now displays its label correctly on user forms. This prevents confusion when users or administrators review calendar privacy settings after a related mail module change affected label visibility.
Original PR description
**Version**: - saas-18.3 **issue**: - The calendar privacy field has no label. **cause**: - after merge this PR https://github.com/odoo/odoo/pull/195101 a new group was added in the mail module, which caused the label to no longer display. **solution**: - Add the new group in the calendar module to restore the label visibility. task-4748282
Refreshing EU OSS tax mappings no longer fails when multiple companies are selected and one company is missing a payable tax account code. This helps accounting teams complete tax setup reliably across company structures.
Original PR description
This error occurs when both companies are selected and `Refresh tax mapping` is clicked under Taxes. Steps to reproduce: --- - Install `l10n_eu_oss` application - Create a NEW Company with EU…
This error occurs when both companies are selected and `Refresh tax mapping` is clicked under Taxes. Steps to reproduce: --- - Install `l10n_eu_oss` application - Create a NEW Company with EU Localizations > Switch to it - Now select both Companies - Invoicing > Configuration > Settings > Taxes > `Refresh tax mapping` Traceback: --- `TypeError: expected string or bytes-like object, got 'bool'` At [1], this error occurs because clicking `Refresh tax mapping` attempts to retrieve the `Tax Payable` account code from both companies. In this case, the code from the parent company is retrieved correctly, but the child company's code is missing (i.e., False). As a result, an error is raised during the process. This commit fixes the above error by ensuring the code is fetched within the appropriate company context. [1]- https://github.com/odoo/odoo/blob/4cadc407c00dfe93af943c70d6d3b07c5ae01929/addons/l10n_eu_oss/models/res_company.py#L46-L49 sentry-6611611716 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects how leave-related numbers are displayed in the Time Off module. It prevents an error caused by treating decimal values as whole numbers, improving reliability when viewing or editing leave allocations.
Original PR description
Before this commit, the widget integer was used for a float and was raised as an error. This commit fix it. 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