Monday, October 13, 2025
38 changes · 19.0
Enhancements to existing features
The HR work entry process has been simplified by no longer requiring a work entry type in cases where it is not needed. This reduces unnecessary setup or data-entry friction for HR teams while keeping the change limited to the work entry area.
Original PR description
Removing unneeded function Task-5107738
The Belgian salary package demo data now aligns Laurie Poiret's login and email information. This avoids duplicate-looking contact details appearing in the user form, making demo records clearer for users reviewing the system.
Original PR description
laurie poiret uses a different login from her email. Which is technically fine but leads to both of them appearing in the user form which we don't want. task-5130854 [related]: odoo/odoo@db3dee12d7c17ad485800d000ec4cdd87fcfd18b
The attendance overtime rule form now prevents users from editing the rate when the Work Entry module is installed. This helps keep overtime calculations consistent and reduces the risk of accidental changes to payroll-related settings.
Original PR description
If Work Entry module is installed --> Make the rate readonly within the form view of the attendance overtime rule. Task-5107738
Payment terminals will no longer be automatically registered for event handling because they already manage those events themselves. This reduces unnecessary setup work and helps avoid duplicate or incorrect event processing for connected payment devices.
Original PR description
As for printers that can send event whenever they want, payment terminals handle event themselves. We then removed auto event registering for payment terminals. odoo/enterprise#96634
Resolved issues and error corrections
This fixes an issue in the Turkish Nilvera integration that could trigger a server error when handling failed HTTP responses. Businesses using this localization should now see the intended error handling instead of an unexpected crash.
Original PR description
The http response object doesn't have a `code` attribute, this commit fixes this typo which has already been fixed in 19.0 as a part of #222869 task-5050516 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#228088
Miscellaneous changes
This change updates an internal test file related to branch targeting and naming. It does not introduce a user-facing product change, but helps keep the development and testing process aligned with current branch conventions.
This change prevents Danish Nemhandel electronic invoicing connections from accidentally using production systems in neutralized environments. Existing proxy clients are switched to demo mode, and new registrations are directed to the test server, reducing operational risk during testing or copied database use.
Original PR description
To avoid sending/registering on production, add a neutralize script. The existing proxy client are put in demo mode. The new connections will be registered on the test server. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#229934
The India localization test setup was adjusted so it no longer depends on the US accounting module when demo data is unavailable. This reduces avoidable test failures and helps keep the India localization more reliable during development and maintenance.
Original PR description
Standalone `l10n_in` tests were failing when running without demo data because outside-India companies (e.g., US) were defaulting to their country-based chart of accounts. This required the `l10n_us_account` module, causing errors when the module was not installed. <img width="518" height="28" alt="image" src="https://github.com/user-attachments/assets/748663a0-f329-459c-b0e8-0c3de7019258" /> This commit adapts the test cases to run without l10n_us_account dependency. task- 5116352 Forward-Port-Of: odoo/odoo#230041
User forms now handle cases where login and email differ more safely, especially when the HR app is installed on databases created during a recent transition. The update prevents setup errors, keeps email/login fields aligned, and adjusts the user image area so the form remains readable.
Original PR description
[1] adds back the login button on the user form when login and email are different. However as the override in hr is based on the new base view, this causes issues for people installing hr if they created their database before that commit was live. The login can be moved inside the email div and simply duplicated so that the hr module doesn't need to know about the new div. Although it may cause the field to appear twice on databases created the week this commit was live, it's a lesser issue than throwing a traceback. Icon margins are also tweaked to be consistent accross base and the hr override task-5130854 [1]: https://github.com/odoo/odoo/commit/db3dee12d7c17ad485800d000ec4cdd87fcfd18b
Maintenance equipment pages now open reliably even when a repaired request has had its close date or request date manually cleared. This prevents customized or manually adjusted records from blocking users while still keeping repair metrics usable.
Original PR description
Using standard Odoo, `maintenance.request.close_date` should never be `False` when its `stage_id == 'done'`, but customizations/manual overrides allow users to force it to be `False` and block them…
Using standard Odoo, `maintenance.request.close_date` should never be `False` when its `stage_id == 'done'`, but customizations/manual overrides allow users to force it to be `False` and block them from opening equipment views that displayed fields that depended on it. Steps to reproduce: - Create new maintenance request for an equipment - Put maintenance request into a `maintenance.stage` where `done=True` (e.g. "Repaired") - Force `close_date` to not be `readonly` in form view + set it to `False` - Try to open the assigned equipment's form view Expected result: Form view opens without issue Actual result: `unsupported operand type(s) for -: 'bool' and 'datetime.date'` Issue was due to `mttr` calculation in `_compute_maintenance_request` not expecting `close_date` to be `False`. Since we want the request to still be considered for the rest of the compute, we count its "Time to Repair" as 0 in this case since we cannot use infinity in this case. Additionally, we also gracefully fail in the same way in case `request_date` is also forced to be `False` since it is not a mandatory field and can cause the same issue. 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#230942 Forward-Port-Of: odoo/odoo#230821
The appraisal skills list now allows horizontal scrolling on mobile, so users can access the justification field and add or remove buttons. This restores important appraisal editing actions for employees and managers using smaller screens.
Original PR description
Horizontal scrolling has been disabled on the appraisal skills list. An unwanted side effect of that is that the justification field along with the add and remove buttons are not visible on mobile. This PR re-enables the scrolling and removes some dead css. task-5001344 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#230430 Forward-Port-Of: odoo/odoo#222161
The color picker now remembers where users last chose a color and opens that same tab the next time. This avoids extra clicks when editing website snippets, text colors, backgrounds, or gradients, making page customization smoother.
Original PR description
*web, website Before this commit, `BuilderColorPicker` had no memory of the last used tab and always opened on the first tab, regardless of whether the user had previously selected a color. After this commit, if the user has done a selection, the color picker opens on the tab of that selection. How to reproduce the problem: 1. Drop a new snippet, e.g. `s_text_block`, 2. Click on the snippet, then open the "Background" color picker 3. Pick a custom color or a gradient 4. If the color picker is stil open, press ESC 5. Open the color picker again 6. PROBLEM: the color picker is opened on the "theme" tab task-4367641 Forward-Port-Of: odoo/odoo#227197
This fixes a Sales module issue where automated checks could fail if a customized sales order line view showed another field before the product field. The change makes the product configurator test flow more resilient, helping prevent false failures for customized Sales setups.
Original PR description
To reproduce: 1. Manually modify the SO view `view_order_form` notebook SO lines list view to make visible any column before `product_id` For example:…
To reproduce:
1. Manually modify the SO view `view_order_form` notebook SO lines list view to make visible any column before `product_id` For example:
https://github.com/odoo/odoo/blob/18.0/addons/sale/views/sale_order_views.xml#L521 making the field `display_type` visible
2. Run the tests of `sale` module
=> `sale` module tests will fail on test `test_sale_combo_configurator_preconfigure_unconfigurable_ptals`
```
FAILED: [18/22] Tour sale_combo_configurator_preconfigure_unconfigurable_ptals → Step Verify that configurable ptals are now configured (trigger:
.sale-combo-configurator-dialog
.combo-item-grid
.product-card:has(.card-title:contains("Test product"))
:contains("Attribute B: B")).
Element (
.sale-combo-configurator-dialog
.combo-item-grid
.product-card:has(.card-title:contains("Test product"))
:contains("Attribute B: B")) has not been found.
TIMEOUT step failed to complete within 10000 ms.
```
see runbot build fail at:
https://runbot.odoo.com/runbot/build/89552334
The issue happen as - for some dark magic JS/XML reason - adding the field before product_id make fail the step to click the checkbox using the span.
Fix was suggested by PIPU to solve/workaround the issue
In practice, this issue was discovered accidentally with a customisation which was willing to add a custom field at the start of the list
opw-5068699
Forward-Port-Of: odoo/odoo#228029The point of sale now shows a clear "Device disconnected" message when the Belgian blackbox is unplugged, instead of a vague unknown error. This helps store staff understand the issue faster and take the right action without confusion.
Original PR description
When the blackbox is being disconnected the user gets "unknown blackbox error" instead of "Device disconnected" explicit message. This PR removes this vague error message introduced in https://github.com/odoo/enterprise/pull/93468 Forward-Port-Of: odoo/enterprise#95587 Forward-Port-Of: odoo/enterprise#95489
This fixes an issue where a date or time range picker in a list could reopen immediately after being closed, forcing users to close it twice. The change makes list editing smoother while keeping the picker opening automatically when a new empty date range is added.
Original PR description
Before this commit, the datetime picker would reopen after being closed, requiring it to be closed a second time. The issue was caused by the list view automatically focusing on the first cell or the…
Before this commit, the datetime picker would reopen after being closed, requiring it to be closed a second time. The issue was caused by the list view automatically focusing on the first cell or the last edited field after the picker was closed. When the <button> element received focus, the activeInput value was updated, causing the <button> to switch to an <input> due to reactivity. As a result of this remounting, the useEffect() hook was triggered, which caused the picker to reopen (see openPicker()). An alternative solution would be to call `leaveEditMode()` before the focus, but that's not feasible since `onGlobalClick` is triggered later, after the update. To fix this, we prevented the list view from automatically focusing the date range field except if the field is empty. This preserves the intended behavior of opening the picker when adding a new item to the list. With this change, after selecting a value in the picker, no focus occurs, and therefore the picker does not reopen after being closed. Steps to reproduce: - Go to "Appointments" - Configure -> Option - Set "Schedule" as "Flexible" - In the "Availabilities" tab, - Add a new line - After selecting a range, close the picker -> The picker is still open task-5080321 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
This update keeps the restaurant appointment floor screen working correctly after related changes in the underlying point-of-sale system. It helps prevent display or interaction issues for restaurant staff managing appointments and floor plans.
Original PR description
This commit adapts an overriding method to reflect changes in the base method done in this pr https://github.com/odoo/odoo/pull/176016. Forward-Port-Of: odoo/enterprise#91334
This fix ensures the Community menu button is properly shown on event forms when the Track Quiz feature is installed. It prevents users from missing a relevant website event option in setups that do not also include the event meeting feature.
Original PR description
In the event form the "community" button is supposed to be shown when "track quiz" is installed. However when this was done in [1] there a mistake was made and only the label was removed, as well as the wrong field added after it. That field was removed in [2] but it was again not noticed that only the label was made visible. It may not appear easily because installing website_event_meet also unhides both the label and the field. Hence you only ge this issue when installing track quiz without it. However in 18.3 [3] removed website_event_meet which means the issue is not corrected anymore. task-5159806 [1]: https://github.com/odoo/odoo/commit/147cf5f328f5a55882a62a4279d1d92511628320 [2]: https://github.com/odoo/odoo/commit/c0f0f9f47573b74ca6b1fcdc3383e43f28f7a2e1 [3]: https://github.com/odoo/odoo/commit/9cab4f8f77f71e405971c184544765e8f252a012 Forward-Port-Of: odoo/odoo#231020
Creating a work entry without selecting a type no longer causes an error. This helps HR users complete scheduling or attendance updates more reliably, even when optional information is missing.
Original PR description
If the user creates a work entry without a work entry type, it will fetch "false" id work entry type. It raises a traceback task-5078885
Demo Discuss messages from Alex now display Alex as the sender instead of Odoobot. This keeps demo conversations accurate and avoids confusion when users review or test the Discuss experience.
Original PR description
Before this commit, Alex's messages in discuss demo data were displayed as "Odoobot" rather than Alex. This happens because message had proper author_guest_id but no author_id defined, thus it had default value Odoobot and since [1] the author_id has precedence over `author_guest_id`. Before [1] there was no bug because the server returned formatted data of a single author as a persona, and guest_author_id had precedence over author_id. [1]: https://github.com/odoo/odoo/pull/211868 Before <img width="811" height="279" alt="Screenshot 2025-10-10 at 16 18 53" src="https://github.com/user-attachments/assets/862cfd18-24a0-485f-89b6-77277b9098ad" /> After <img width="815" height="280" alt="Screenshot 2025-10-10 at 16 17 45" src="https://github.com/user-attachments/assets/f83b98dd-ffb1-4419-851c-f34f3261792d" /> Forward-Port-Of: odoo/odoo#231047
This fixes an internal test issue where payment follow-up report checks could fail if they ran across midnight. The change helps keep automated validation stable without changing customer-facing behavior.
Original PR description
Tests https://runbot.odoo.com/odoo/runbot.build.error/159772 where failing when setUpClass run before midnight and the test itself run at/after midnight because `today` was not the same. As follow-up report divides the lines per partner to due/overdue utilizing `today` in comparison, This resuls in different lines than expected. Forward-Port-Of: odoo/enterprise#96486
Salary rules now prevent changing the salary structure once the rule is linked to an employee property. This helps avoid accidental payroll configuration changes that could affect employee salary calculations.
Original PR description
As some other `hr.salary.rule` fields (like Section and Unit), Salary Structure is now readonly when the rule has a property on an employee. 5135927 [task-5135927](https://www.odoo.com/odoo/project/1251/tasks/5135927)
Mexican DIOT reports now correctly identify suppliers or records from the United Kingdom instead of grouping them under "Other country." This helps businesses produce more accurate tax reporting and reduces the risk of manual corrections.
Original PR description
The DIOT country adaptation map lacked the ISO 3-letter code for the UK, causing records with country 'GB' to be reported as 'ZZZ' ("Other country").
Added mapping 'GB' → 'GBR' to ensure correct DIOT country code generation.
Forward-Port-Of: odoo/enterprise#96771When a website is configured only for events, the ecommerce app is no longer installed automatically. This avoids adding unnecessary sales features and keeps the website setup aligned with the user's selected purpose.
Original PR description
Steps to reproduce: 1. Install website module 2. Select events in configurator 3. Build website. => Ecommerce is installed, which should not as it does not make sense with only the events. After this commit: - Ecommerce will no longer be installed when the events is configured. task-4922600 Forward-Port-Of: odoo/odoo#221527
Belgian payroll rules were updated so deduction 3000 uses the correct values through July 2025. This helps keep payroll calculations aligned with current Belgian requirements and reduces the risk of incorrect payslips.
Draft payslips can now be saved even when the payslip period date is left empty. This prevents an unexpected error during payroll preparation and keeps the payslip editing flow reliable.
Original PR description
When removing the date in a draft payslip an exception was raised. This was fixed and a test was added to check the flow. task-5159666
The online shop category sidebar now keeps nested category items within the correct width, even when category names are long. This prevents layout distortion and keeps product browsing pages visually consistent for shoppers.
Original PR description
__Issue:__ In the product categories sidebar (`#products_grid_before`), nested `<li>` elements could become wider than their parent `<ul>` when the category names were long (e.g., "Untersuchungshandschuhe"). This caused the parent <ul> to expand in height before the child and broke the visual layout. __Fix:__ Force `<li>` elements inside the `#categories_recursive` list to respect their parent width by applying `width: 100%` This keeps the sidebar layout consistent even with long category names. - opw-5075226 Forward-Port-Of: odoo/odoo#228343
This fix prevents Odoo 19 from failing during startup on Python 3.11 and later because of a changed web address handling dependency. It helps businesses run Odoo reliably on supported modern Python environments without encountering this import error.
Original PR description
Description of the issue/feature this PR addresses: - In Python 3.11+, urllib3 stopped relying on its internal _WHATWG_C0_CONTROL_OR_SPACE constant directly in newer releases Current behavior before PR: - As described in #230990 Desired behavior after PR is merged: - Running Odoo19 on Python 3.11+ should not throw a `_WHATWG_C0_CONTROL_OR_SPACE missing` error --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents users from creating a to-do item without a name, avoiding an error that could appear during quick creation. It also adds a safeguard for existing records with missing names so they no longer trigger the same failure.
Original PR description
Currently, an error occurs when user tries to create a to-do with no name. Steps to replicate: - Install Project. - Go to `To-Do > Click New > Click Add`. - Error will occur on the terminal. Error:…
Currently, an error occurs when user tries to create a to-do with no name. Steps to replicate: - Install Project. - Go to `To-Do > Click New > Click Add`. - Error will occur on the terminal. Error: `TypeError: expected string or bytes-like object, got 'bool'` Cause: - The error occurs after a recent [PR], that changed `name` field in the to-do app's kanban view to `display_name`. - As `display_name` is not a required field this will allow the creation of task and trigger the method `_inverse_display_name`. - This will cause the error to occur at line [1] (because `task.display_name` is False). Solution: - Made the field required through xml similar to the `project.task` kanban view in the project app [2]. - Also handled the case when `display_name` is received falsy at [1] by skipping the execution and continuing the loop (this is mostly for the existing DBs). [PR]: https://github.com/odoo/odoo/pull/205354 [1]: https://github.com/odoo/odoo/blob/b81d119fae5f5194334cee94bacffefeb1cd8c6e/addons/project/models/project_task.py#L801 [2]: https://github.com/odoo/odoo/blob/b81d119fae5f5194334cee94bacffefeb1cd8c6e/addons/project/views/project_task_views.xml#L609 sentry-6913627252 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Creating a company in the Belgium localization no longer crashes when an alphanumeric ZIP code is entered. The system now skips region calculation for invalid Belgian ZIP codes, preventing disruption during company setup.
Original PR description
Currently, in the Belgium localization, creating a company with an alphanumeric ZIP code raises an error. **Steps to Reproduce:** 1) Install **account,l10n_be_reports** module 2) Navigate to…
Currently, in the Belgium localization, creating a company with an alphanumeric ZIP code raises an error. **Steps to Reproduce:** 1) Install **account,l10n_be_reports** module 2) Navigate to **Settings>Users & Companies>Companies**. 3) Create a New Company and first set country as `Belgium` and then set a alpha-numeric value to `ZIP=(e.g. R93R2R3)` 4) Click anywhere on the screen **Error:** `ValueError: invalid literal for int() with base 10: 'R93R2R3'` **Root Cause:** since [this commit](https://github.com/odoo/enterprise/pull/93219/commits/d9f116b5ceda85a11c997b8d46ec9af5425cbf09), a new field `l10n_be_region_id` is computed based on zip as shown at [1]. When an alphanumeric `ZIP` is added, the computation searches the company region based on `zip_start` and `zip_end` as shown at [1]. However, `zip_start` and `zip_end` expect integer values only, as mentioned at [2], which causes the error. **Fix:** Prevent calculation of region for companies with invalid zip code for belgium localization. [1]- https://github.com/odoo/enterprise/blob/424a470188756fffed4437b83d127039795fbe59/l10n_be_reports/models/res_company.py#L37-L45 [2]- https://github.com/odoo/enterprise/blob/71cc92c9526234dcd44ec756375647a67729029f/l10n_be_reports/models/l10n_be_company_region.py#L17-L18 sentry-6931185627
This fix updates test data so products are treated as properly configured for manufacturing instead of missing setup details. It prevents false test failures caused by inflated lead times, helping keep planning and rental workflows reliable during validation.
Original PR description
This PR addresses the issue where tests were failing due to unconfigured products (no vendor/ no BoM). Now unconfigured products' lead_time is incremented by 365 due to this PR: https://github.com/odoo/odoo/pull/216293 Before this fix: Products have `buy` route by default and no vendor, so they are considered unconfigured products and lead time is incremented by 365, and tests fail as any lead time refers to a date earlier than today would only affect the first period in the MPS which is not intended in the tests. After this fix: Products have `manufacture` route and there is BoM, so they are considered configured products and lead time is calculated normally from BoM which is 0. Task-4779057 Forward-Port-Of: odoo/enterprise#88766
Employee contracts in multi-company setups now only show insurance options that belong to the relevant company. This prevents users from accidentally selecting insurance records from another company, improving payroll data accuracy.
Original PR description
Currently, in a multi-company setup, you are able to select insurances from other companies on the employee contract task-5157106 Forward-Port-Of: odoo/enterprise#96932 Forward-Port-Of: odoo/enterprise#96821
Fixes an issue in the HTML editor where undoing image rotations, resizing, or dragging required several undo actions. Users can now press Ctrl+Z once to restore the image to its original state, making content editing more predictable and efficient.
Original PR description
**Current behavior before PR:** - When rotating, resizing, or dragging an image using the transform container, pressing Ctrl+Z did not revert the image to its initial state (when the transform container was opened). - Instead, it required multiple undo operations to return to the initial state. **Desired behavior after PR is merged:** - Pressing Ctrl+Z now correctly reverts the image to its initial state in a single undo, after a transformation. task-5114320 Forward-Port-Of: odoo/odoo#230211 Forward-Port-Of: odoo/odoo#228720
This update ensures multiple quote carousel sections on a website page each get their own unique identifier. As a result, navigation controls like next and previous now operate the correct carousel instead of accidentally moving another one.
Original PR description
The selector used to target the carousel, to generate unique ID, did not include some carousels (s_quotes[...]). This led to issues with the controllers that would not be linked to the correct carousel. Steps to reproduce the issue: - Go to Edit - Drop two "s_quotes_carousel" - Save - Click on the "next" arrow of the second carousel => The second carousel does not slide, but the first one does. Forward-Port-Of: odoo/odoo#230541
Phone numbers in the VoIP call list now stay properly aligned when no country flag is shown. This removes a small visual offset that affected calls to invalid or unrecognized numbers, making the list easier to read.
Original PR description
In the voip.call list view, when no flag is displayed, the phone number is slightly offset to the right. This is because the margin that separates the flag from the phone number is still present. This commit moves the margin from the phone number (always displayed) to the flag (sometimes absent). How to reproduce: 1. Make a call to an invalid phone number 2. Go to voip.call list view 3. Look at the numbers without a flag
The command palette now keeps all repeated characters visible when highlighting search matches in app names. This prevents confusing or misspelled-looking results, such as “Meeting Rooms” appearing with a missing letter during search.
Original PR description
**Before this commit :** When searching for apps whose names contain repeated characters, the command palette incorrectly omitted the second occurrence of that repeated character while searching for it. Example: App name: Meeting Rooms input: o Result: Meeting Roms(missing the second `o`), which was incorrect. **After this commit:** The command palette now correctly displays all characters without skipping any repeated ones. task-5129947 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix reduces the risk of duplicate commission achievement records being generated when subscription commission adjustments happen close together. It helps keep commission reporting accurate and avoids conflicts that could affect sales compensation calculations.
Original PR description
This commit 5b6fdda126e4cfa5ebf92f7b96d1805f6c4b992b introduce an entropy date to avoid having two separate achievment.report record with the same ID. Entropy date for log where based on the write_date, this commit 03d1ee3495a4936fbff0d21743bb784c85b50b12 add the sign of the amount. Unfortunatly this is not enough, the adjustment after the transfer can be positive as well and thus two achievment ends-up with the same ID anyway. This commit use the id of the log to add more entropy to the entropy_date, since log are created in the same transaction, they are likely to have id just seperate by one or only few number, id % 10 seems enough, therefore two log on the same order, with the same create_date will have different entropy date and end up with a different id. Forward-Port-Of: odoo/enterprise#96622
Fixes the default end date used in sales commission achievement reports so it consistently uses the latest end date across relevant commission plans. This helps ensure reports cover the full intended period and avoids accidentally cutting off commission data too early.
Original PR description
When there is active_plan_ids in the context the date_to are the max of plans' date_to when not it's the min, this is wrong it should be the maw as well Forward-Port-Of: odoo/enterprise#96526
SEPA payment files will now mark payments as high priority only for Belgian companies. This helps companies in other countries avoid unnecessary bank fees that can be charged for high-priority payments.
Original PR description
Having priority set as HIGH for SEPA payments can induce extra fees (ex. in CH). This commit only sets the priority to HIGH for BE companies. task-4874217 Forward-Port-Of: odoo/enterprise#96869 Forward-Port-Of: odoo/enterprise#95420