Odoo Changelog — 2026-06-29

Monday, June 29, 2026

3 changes · saas-18.3

Improvements(3)

Enhancements to existing features

[IMP] hr_holidays : improve leave validity error message

PR #271915

Coresaas-18.3hr_holidaysMEDIUM

When a leave update fails, the system now provides more useful details about which employee’s leave caused the issue. This makes it much easier for customers and support teams to identify and resolve allocation or time-off balance problems without manually checking every record.

Original PR description

The current message is pretty useless as of now when a lot of leaves are being written to, notably when creating a public holiday, which sets the state of all the leaves overlapping the public holiday's day to be reevaluated, and if an error occurs, you have to go through every employee's leave allocation and leaves taken to hopefully find one who might have to many days taken/not enough allocated.

This extra information will be a huge QOL improvement, for the customer who will be able to troubleshoot his issue himself more easily, but also for our support team as the only way to debug those kind of issues now is to put a breakpoint there and see what employee has an issue.

opw-4411999

Forward-Port-Of: odoo/odoo#270888
Forward-Port-Of: odoo/odoo#200376

#time off#error message#support#usability

[IMP] sql_db: make MAX_IDLE_TIMEOUT configurable

PR #272553

Coresaas-18.3sql_dbMEDIUM

This change lets operators adjust how long unused database connections stay open. It helps systems with limited memory release idle connections sooner, which can improve stability and reduce resource usage.

Original PR description

In memory-scarce environments, the default 10-minute idle timeout may keep too many backend connections alive. Allow operators to override it via the ODOO_DB_MAX_IDLE_TIMEOUT environment variable to evict idle connections more aggressively.

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

Forward-Port-Of: odoo/odoo#271785

#database#performance#memory#connections

[IMP] l10n_fr_pdp: move pdp response button to cog wheel

PR #272274

Coresaas-18.3l10n_fr_pdp

The action used to send a PDP response is no longer shown as a large button on the invoice/bill screen. It is now available in the settings/menu options, reducing visual clutter while keeping the same functionality through other posting and cancellation actions.

Original PR description

No real need to show a big button for sending a response in PDP as cancelling and posting an invoice/bill would do the same, so we move it to the cog wheel menu

task-6274220

Forward-Port-Of: odoo/odoo#268846

#ui#invoice#bill#pdp#menu

The current message is pretty useless as of now when a lot of leaves are being written to, notably when creating a public holiday, which sets the state of all the leaves overlapping the public holiday's day to be reevaluated, and if an error occurs, you have to go through every employee's leave allocation and leaves taken to hopefully find one who might have to many days taken/not enough allocated. This extra information will be a huge QOL improvement, for the customer who will be able to troubleshoot his issue himself more easily, but also for our support team as the only way to debug those kind of issues now is to put a breakpoint there and see what employee has an issue. opw-4411999 Forward-Port-Of: odoo/odoo#270888 Forward-Port-Of: odoo/odoo#200376

In memory-scarce environments, the default 10-minute idle timeout may keep too many backend connections alive. Allow operators to override it via the ODOO_DB_MAX_IDLE_TIMEOUT environment variable to evict idle connections more aggressively. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#271785

No real need to show a big button for sending a response in PDP as cancelling and posting an invoice/bill would do the same, so we move it to the cog wheel menu task-6274220 Forward-Port-Of: odoo/odoo#268846