Wednesday, September 2, 2026
4 changes · saas-19.4
Enhancements to existing features
Timesheet timers now suggest tasks based only on recent activity from the past month, instead of pulling in tasks last used a long time ago. This helps employees log time faster and reduces mistakes caused by outdated task suggestions.
Original PR description
When selecting a project in the timesheet timer, the prefilled task could be one the user last logged time on years ago, which is no longer relevant. The prefill now only considers timesheets from the past month and follows the user's most recent one: if that timesheet has no task, none is prefilled rather than reaching further back. task-6485260 Forward-Port-Of: odoo/enterprise#128738
This change helps Odoo handle many simultaneous real-time server tasks without running into connection pool limits. It reduces the risk of service interruptions or errors when usage spikes, especially for live communication features such as bus/websocket traffic.
Original PR description
make gevent connection pool non-blocking to avoid 'The Connection Pool Is Full' error when too many coroutines are borrowing connections in gevent server. https://github.com/odoo/iap-apps/pull/1827 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
The timesheet assistant now favors recent work patterns over old historical matches, so suggested projects and tasks better reflect current assignments. It also keeps stored suggestion data leaner and improves detection rules for Odoo.sh staging-style databases.
Original PR description
Previously, the timesheet assistant's local configuration matched activities to projects/tasks using a strict historical tally. A match made 6 months ago carried the exact same mathematical weight as a match made today. This caused old habits to stubbornly override new assignments. This commit introduces an exponential time-decay algorithm to the frequency computation: - Matches are now weighted based on their `datetime` stamp. - The weight drops by 50% every 5 days (half-life algorithm). - Recent timesheet entries quickly accumulate enough fractional votes to surpass the decayed votes of older, outdated projects. in this commit i updated the matching of local rules to be case sensitive for better matching (eg. "Meeting with client" is the same as "meeting with client") Task: 6267713 Forward-Port-Of: odoo/enterprise#129631 Forward-Port-Of: odoo/enterprise#124669
Businesses in Ecuador can now record their third-party billing software provider's RUC in invoicing settings. The value is automatically included on electronic documents and printed RIDE reports, including delivery guides, helping comply with SRI reporting requirements.
Original PR description
Purpose: SRI Resolution requires taxpayers using 3rd-party billing software in Ecuador to report the software provider's RUC on all electronic documents and printed representations (RIDE). A new system parameter is introduced and displayed in Invoicing > Setting > Ecuadorian Localization > Electronic Invoicing, so users can add their software provider's RUC. This value will be automatically sent to the EDI and displayed on the report. task-6432810 Forward-Port-Of: odoo/enterprise#129456