Saturday, August 22, 2026
8 changes · 19.0
Enhancements to existing features
Adds a dedicated screen for French PDP e-reporting moves so users can review key e-reporting details separately from the standard accounting move view. This improves visibility for compliance-related information while keeping the main accounting view unchanged.
Original PR description
This commit will add a new view for the ereporting moves to be able to see some specific info without touching the base move view. task-6274213 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#270101
This update improves internal tests that validate scheduled marketing automation work, helping ensure campaigns process consistently over time. It also corrects how configuration settings are referenced in these tests, reducing the risk of false failures or missed issues before release.
Resolved issues and error corrections
This fixes a crash when work-hour values close to the next hour were converted into clock times. The change makes time calculations more reliable for computed or aggregated hour values, especially near hour and day boundaries.
Original PR description
### Bug `odoo.tools.date_utils.float_to_time` builds the minutes with a rounding step: ```python return time(int(integral), int(float_round(60 * fractional, precision_digits=0)), 0) ``` When the…
### Bug
`odoo.tools.date_utils.float_to_time` builds the minutes with a rounding step:
```python
return time(int(integral), int(float_round(60 * fractional, precision_digits=0)), 0)
```
When the fractional part of the hour is high enough, `round(60 * fractional)`
rounds up to a full **60**, and `time(hour, 60)` is invalid:
```python
>>> float_to_time(16.9959)
ValueError: minute must be in 0..59, not 60
>>> float_to_time(8.999)
ValueError: minute must be in 0..59, not 60
```
Any hours value whose fractional part is ≥ ~0.9917 hits this — which happens
easily with computed/aggregated work-hour floats.
### Fix
Carry the rounded-up minute into the hour, and return `time.max` when that carry
reaches the end of the day (mirroring the existing `hours == 24.0` case):
```python
if minute == 60:
hour += 1
minute = 0
if hour >= 24:
return time.max
```
`float_to_time(16.9959)` now returns `time(17, 0)`, `float_to_time(23.9959)`
returns `time.max`, and regular values are unchanged.
Adds `TestFloatToTime` in `test_date_utils.py` covering the carry, the
end-of-day carry, and regular values.Documentation and clarification updates
This pull request records Waqas Ahmed's signed Contributor License Agreement. It supports the legal requirements for accepting future contributions and has no direct impact on product features or users.
Original PR description
Contributor License Agreement for Waqas Ahmed I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes the Turkish Nilvera localization explicitly include a required e-invoicing component. It prevents installation and testing failures in environments where automatic module installation is skipped, improving reliability without changing business workflows.
Original PR description
The view 'res.partner.property.form.inherit.ubl.tr' references external ID 'account_edi_ubl_cii.view_partner_property_form' but module 'account_edi_ubl_cii' is only available because of auto_install-links in the module graph. This causes an error when auto_install is skipped on runbot. The error is fixed since saas-19.2(https://github.com/odoo/odoo/pull/248034) where the view is moved but no backport for saas-19.1 and earlier has been made. Adding the explicit dependency is valid because 'account_edi_ubl_cii' is indirectly installed at the same time. This is the effect chain: 1. 'l10n_tr_nilvera_einvoice' is auto_install'ed after 'l10n_tr_nilvera' installs 2. 'l10n_tr_nilvera_einvoice' has explicit dependency on 'account_edi_ubl_cii'. Forward-Port-Of: odoo/odoo#282475
This fix updates how image palette handling is referenced so it works with the Pillow version included in Ubuntu Jammy as well as newer versions. It helps keep automated image-related tests reliable across supported environments without changing user-facing behavior.
Original PR description
`Image.Palette.ADAPTIVE` is not available in the Pillow version provided by Ubuntu Jammy, causing the animated GIF test to fail. Use `Image.ADAPTIVE` instead, which is compatible with both older and newer Pillow versions. 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#282223
Tax return submission no longer gets blocked by incomplete account settings on tax groups that have not been used in any transactions. This lets businesses close taxes without fixing irrelevant tax group configurations.
Original PR description
…ax closing Steps to reproduce: - Remove the tax payable and receivable accounts of a tax group for which no move exists. - Open the tax returns view, set the opening date and submit the tax return -> Odoo prevents going further because the tax group configuration isn't fully done, but it's useless to ensure that for tax groups that aren't used.
This fix ensures Brazilian point-of-sale tax adjustment entries use the correct sales tax when matching tax codes. It prevents accounting entries from becoming unbalanced when similar sales and purchase taxes exist, improving reliability of fiscal records.
Original PR description
The chart template gives the same Avatax code and price_include_override to the sale and the purchase tax, and creates both in the same transaction. Without an explicit type_tax_use the lookup used to return either of them at random, and picking the purchase one left the entry unbalanced. The purchase taxes got their Avatax code in 18.4+. https://github.com/odoo/enterprise/pull/101072 runbot-945969 Forward-Port-Of: odoo/enterprise#128476