Odoo Changelog — 2026-08-10

Monday, August 10, 2026

2 changes · saas-18.4

Bug Fixes(2)

Resolved issues and error corrections

[FIX] core: Extend mapping of legacy time zone names

Coresaas-18.4base

This fix keeps Odoo compatible with newer operating system time zone data by linking older time zone names to their current equivalents. It helps prevent runtime errors and test failures after system updates, with no expected change for most users.

Original PR description

In ubuntu 26.04 the time zone database contents changed. A couple of 
timezone names are not available anymore, causing runtime exceptions.
This mapping links old with new time zone naming conventions to prevent
future (test) breakdown.

The mapping WET to Europe/Lisbon is imperfect, and the localizations for
the fixed date inside the test did not match. There exists no better nor
correct mapping for WET. The mapping to Europe/Lisbon comes from the
IANA tzdb-2026c and is official, so it is kept unchanged.
The fixed date inside the test is changed to a recent one that aligns
the test outcome with expectations:
- Offsets match for recent history and future time
- Match daylight savings time (DST) observation

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#280691

#time zones#compatibility#Ubuntu

[FIX] sign: Fix to-sign count not decreasing after signing in portal

PR #126932

Enterprisesaas-18.4sign

The portal now correctly lowers a user's to-sign count after they complete their part of a document. This prevents signed documents from appearing as still awaiting that user's action, improving clarity for portal users.

Original PR description

Version: 18.0

Steps to reproduce:
- Create a sign request with two signers.
- Assign the first signature to a portal user.
- Log in as the portal user and sign the document.

Issue:
After signing, the to-sign count in the portal does not decrease. This is because the query only checks the overall sign request state instead of the individual signer's item state, so the count remains unchanged

Fix:
Added an item level state check to the count query so it only counts items that are still pending for that specific user.

Task ID: 6412976

Forward-Port-Of: odoo/enterprise#125632

#portal#signatures#document signing

In ubuntu 26.04 the time zone database contents changed. A couple of timezone names are not available anymore, causing runtime exceptions. This mapping links old with new time zone naming conventions to prevent future (test) breakdown. The mapping WET to Europe/Lisbon is imperfect, and the localizations for the fixed date inside the test did not match. There exists no better nor correct mapping for WET. The mapping to Europe/Lisbon comes from the IANA tzdb-2026c and is official, so it is kept unchanged. The fixed date inside the test is changed to a recent one that aligns the test outcome with expectations: - Offsets match for recent history and future time - Match daylight savings time (DST) observation --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#280691

Version: 18.0 Steps to reproduce: - Create a sign request with two signers. - Assign the first signature to a portal user. - Log in as the portal user and sign the document. Issue: After signing, the to-sign count in the portal does not decrease. This is because the query only checks the overall sign request state instead of the individual signer's item state, so the count remains unchanged Fix: Added an item level state check to the count query so it only counts items that are still pending for that specific user. Task ID: 6412976 Forward-Port-Of: odoo/enterprise#125632