Odoo Changelog — 2026-05-21

Thursday, May 21, 2026

4 changes · saas-18.4

Bug Fixes(4)

Resolved issues and error corrections

[FIX] mrp_mps: handle whitespace on forecast/replenish cells

Enterprisesaas-18.4mrp_mps

This update resolves an issue where users could trigger an error when entering spaces in the 'Forecasted Demand' or 'Forecasted Stock' cells within the Master Production Schedule. The fix ensures that blank input is handled correctly, preventing the error and maintaining data integrity. This improves the user experience when updating these critical planning figures.

Original PR description

## Steps to Reproduce:
1. Install `mrp_mps` module.
2. Manufacturing > Planning > Master Production Schedule
3. Click on "Forecasted Demand" or "Forecasted Stock" of any product.
4. Click `<SPACE>` and then `<ENTER>`.

## Error:
`ValueError: could not convert string to float: ' '`

## Cause:
When a user enters whitespace(' ') in a **Forecasted Demand** or **Forecasted Stock** cell, the string bypasses the existing `isNaN/empty` checks at [1]. Then the raw whitespace string passes to the ORM call, where `float(' ')` raised a ValueError.

## Fix:
This commit trims the value so that blank input is treated the same as an empty string, and the cell reverts to its original value.

[1] - https://github.com/odoo/enterprise/blob/6ae5d3df6e9305416e4d6f74259cd01753025f42/mrp_mps/static/src/components/line.js#L128

sentry-7473062917

Forward-Port-Of: odoo/enterprise#117052

#planning#forecasting#production schedule

[FIX] helpdesk: prevent error when creating a helpdesk team

PR #117848

Enterprisesaas-18.4helpdesk

This update fixes an error that occurred when creating new Helpdesk teams. Specifically, the system would fail if the default 'Helpdesk: Ticket Received' email template was missing. The change ensures the template exists before attempting to use it, preventing the error and allowing team creation to proceed smoothly.

Original PR description

Currently, an error occurs when a user tries to create a helpdesk team record.

**Steps to Reproduce:**

 - Install the `helpdesk` module without demo data.
 - Go to `Settings` > `Technical` > `Email` > `Email Templates` and delete the 
   `Helpdesk: Ticket Received` template record.
 - Go to `Helpdesk` > `Configuration` > `Stages` and remove all records.
 - Go to `Helpdesk` > `Configuration` > `Helpdesk Teams` and click `New` to create a record.

`AttributeError: 'NoneType' object has no attribute 'id'`

When the user deletes all stages, the system attempts to create a new stage and assign the 
"Helpdesk: Ticket Received" mail template to it [1]. However, if this template record does not 
exist, accessing its id raises the error.

This commit ensures that the template record exists before accessing its id, otherwise, None is 
passed as the default value.

[1]: https://github.com/odoo/enterprise/blob/32187f79fb0a595497a5e77db4b22b417b03b8dd/helpdesk/models/helpdesk_team.py#L34

sentry-7482994877

Forward-Port-Of: odoo/enterprise#117446

#helpdesk#template#error

[FIX] mrp_workorder: hide manufacturing control types for invalid QC

PR #117961

Enterprisesaas-18.4mrp_workorder

This update corrects a bug where certain quality control test types were incorrectly displayed during work order creation. The change ensures these test types are only available for manufacturing operations, improving data accuracy and preventing users from selecting inappropriate options. This resolves an issue identified through testing.

Original PR description

### Issue: The `Print Label`, `Register Production`, `Register By-products`and `Register Consumed Materials` are all available in the test types at control point creation. ### Expected behavior:…

### Issue:

The `Print Label`, `Register Production`, `Register By-products`and `Register Consumed Materials` are all available in the test types at control point creation.

### Expected behavior:

These test types are only meant for manufacturing operations and are supposed to be hidden by the field domain:
https://github.com/odoo/enterprise/blob/f56aa85b4ad32c5d9ad5593df1366d72e88da0e4/mrp_workorder/models/quality.py#L102-L104 https://github.com/odoo/enterprise/blob/00d6cccd75c402378698a6fd11ee2692f2361c7f/mrp_workorder/models/quality.py#L20-L24

### Cause of the issue:

Since saas-18.1: 5ef007a2116e528b796ebe80fb291ba5f1a94c8f domains are optimised into equivalents SQL clause with better sql performances. This optimization results in the following match for boolean fields: 
`('field', '=', True)` -> `('field', 'in', OrderedSet([True]))` 
`('field', '=', False)` -> `('field', ' not in', OrderedSet([True]))`
Because of these:
https://github.com/odoo/odoo/blob/82b16e8feb3d60a9a3855e3adb3164ae5a6c041d/odoo/orm/domains.py#L1058-L1079 https://github.com/odoo/odoo/blob/82b16e8feb3d60a9a3855e3adb3164ae5a6c041d/odoo/orm/domains.py#L1215-L1236
Now the issue is that the specific `search_method` of the `allow_registration` field is then called with this optimized domain: https://github.com/odoo/odoo/blob/82b16e8feb3d60a9a3855e3adb3164ae5a6c041d/odoo/orm/domains.py#L860-L866 https://github.com/odoo/enterprise/blob/00d6cccd75c402378698a6fd11ee2692f2361c7f/mrp_workorder/models/quality.py#L20-L24
And since `value` is defined as a non empty ordered set in both cases it the search method returns a True leaf as search domain.

opw-5915197

Forward-Port-Of: odoo/enterprise#117068

#quality control#manufacturing

[FIX] documents_account: fix xml document preview with embedded pdf

PR #114759

Enterprisesaas-18.4documents_account

This update resolves an issue where the Documents app's PDF preview was incorrectly displaying a duplicate iframe. The fix ensures that the preview accurately shows the embedded PDF, regardless of how the document was initially received (email or manual upload). This improves the user experience when viewing documents.

Original PR description

**Steps to reproduce:** - Install documents_account - Set up alias to catch incoming mails - Receive a mail with xml attachement which can be previewed as pdf - Go to Documents app - Click on the…

**Steps to reproduce:**
- Install documents_account
- Set up alias to catch incoming mails
- Receive a mail with xml attachement which can be previewed as pdf
- Go to Documents app
- Click on the document preview
- Preview is split in two iframes, both with the same content (pdf)

**Issue:**
Due to the `isPdf` patch the attachment can match multiple types for the preview (pdf and text) as both getter return `true`.
```
<iframe t-if="state.file.isPdf" ...
<iframe t-if="state.file.isText" ...
```

It also seems that xml received by mail are imported as text, which is why the issue doesn't happen when manually uploading the same xml file.

**Fix:**
Ensure that if the document is matching `isPdf`, it doesn't trigger the second iframe with `isText`.

Behavior changed in 18.4 as the text iframe is replaced by this xpath:
`<xpath expr="//iframe[@t-if='state.file.isText']" position="replace">`
which was added for https://github.com/odoo/enterprise/commit/de614ee5e9a087d49939c65c0118ae6164c7b31b
Due to this we also need to ensure `isMimetypeTextual` iframe is not added if `isText` is `false`.

related patch: https://github.com/odoo/enterprise/commit/ffcdd2275c8bf564e15151ccbcaf3965ed968450
fixed by this in 19.0+: https://github.com/odoo/enterprise/commit/3fab4f8f328797fbf11503b975f914ac29da9315

opw-6018536

Forward-Port-Of: odoo/enterprise#113845
Forward-Port-Of: odoo/enterprise#112041

#documents#pdf#preview

## Steps to Reproduce: 1. Install `mrp_mps` module. 2. Manufacturing > Planning > Master Production Schedule 3. Click on "Forecasted Demand" or "Forecasted Stock" of any product. 4. Click `<SPACE>` and then `<ENTER>`. ## Error: `ValueError: could not convert string to float: ' '` ## Cause: When a user enters whitespace(' ') in a **Forecasted Demand** or **Forecasted Stock** cell, the string bypasses the existing `isNaN/empty` checks at [1]. Then the raw whitespace string passes to the ORM call, where `float(' ')` raised a ValueError. ## Fix: This commit trims the value so that blank input is treated the same as an empty string, and the cell reverts to its original value. [1] - https://github.com/odoo/enterprise/blob/6ae5d3df6e9305416e4d6f74259cd01753025f42/mrp_mps/static/src/components/line.js#L128 sentry-7473062917 Forward-Port-Of: odoo/enterprise#117052

Currently, an error occurs when a user tries to create a helpdesk team record. **Steps to Reproduce:** - Install the `helpdesk` module without demo data. - Go to `Settings` > `Technical` > `Email` > `Email Templates` and delete the `Helpdesk: Ticket Received` template record. - Go to `Helpdesk` > `Configuration` > `Stages` and remove all records. - Go to `Helpdesk` > `Configuration` > `Helpdesk Teams` and click `New` to create a record. `AttributeError: 'NoneType' object has no attribute 'id'` When the user deletes all stages, the system attempts to create a new stage and assign the "Helpdesk: Ticket Received" mail template to it [1]. However, if this template record does not exist, accessing its id raises the error. This commit ensures that the template record exists before accessing its id, otherwise, None is passed as the default value. [1]: https://github.com/odoo/enterprise/blob/32187f79fb0a595497a5e77db4b22b417b03b8dd/helpdesk/models/helpdesk_team.py#L34 sentry-7482994877 Forward-Port-Of: odoo/enterprise#117446

### Issue: The `Print Label`, `Register Production`, `Register By-products`and `Register Consumed Materials` are all available in the test types at control point creation. ### Expected behavior: These test types are only meant for manufacturing operations and are supposed to be hidden by the field domain: https://github.com/odoo/enterprise/blob/f56aa85b4ad32c5d9ad5593df1366d72e88da0e4/mrp_workorder/models/quality.py#L102-L104 https://github.com/odoo/enterprise/blob/00d6cccd75c402378698a6fd11ee2692f2361c7f/mrp_workorder/models/quality.py#L20-L24 ### Cause of the issue: Since saas-18.1: 5ef007a2116e528b796ebe80fb291ba5f1a94c8f domains are optimised into equivalents SQL clause with better sql performances. This optimization results in the following match for boolean fields: `('field', '=', True)` -> `('field', 'in', OrderedSet([True]))` `('field', '=', False)` -> `('field', ' not in', OrderedSet([True]))` Because of these: https://github.com/odoo/odoo/blob/82b16e8feb3d60a9a3855e3adb3164ae5a6c041d/odoo/orm/domains.py#L1058-L1079 https://github.com/odoo/odoo/blob/82b16e8feb3d60a9a3855e3adb3164ae5a6c041d/odoo/orm/domains.py#L1215-L1236 Now the issue is that the specific `search_method` of the `allow_registration` field is then called with this optimized domain: https://github.com/odoo/odoo/blob/82b16e8feb3d60a9a3855e3adb3164ae5a6c041d/odoo/orm/domains.py#L860-L866 https://github.com/odoo/enterprise/blob/00d6cccd75c402378698a6fd11ee2692f2361c7f/mrp_workorder/models/quality.py#L20-L24 And since `value` is defined as a non empty ordered set in both cases it the search method returns a True leaf as search domain. opw-5915197 Forward-Port-Of: odoo/enterprise#117068

**Steps to reproduce:** - Install documents_account - Set up alias to catch incoming mails - Receive a mail with xml attachement which can be previewed as pdf - Go to Documents app - Click on the document preview - Preview is split in two iframes, both with the same content (pdf) **Issue:** Due to the `isPdf` patch the attachment can match multiple types for the preview (pdf and text) as both getter return `true`. ``` <iframe t-if="state.file.isPdf" ... <iframe t-if="state.file.isText" ... ``` It also seems that xml received by mail are imported as text, which is why the issue doesn't happen when manually uploading the same xml file. **Fix:** Ensure that if the document is matching `isPdf`, it doesn't trigger the second iframe with `isText`. Behavior changed in 18.4 as the text iframe is replaced by this xpath: `<xpath expr="//iframe[@t-if='state.file.isText']" position="replace">` which was added for https://github.com/odoo/enterprise/commit/de614ee5e9a087d49939c65c0118ae6164c7b31b Due to this we also need to ensure `isMimetypeTextual` iframe is not added if `isText` is `false`. related patch: https://github.com/odoo/enterprise/commit/ffcdd2275c8bf564e15151ccbcaf3965ed968450 fixed by this in 19.0+: https://github.com/odoo/enterprise/commit/3fab4f8f328797fbf11503b975f914ac29da9315 opw-6018536 Forward-Port-Of: odoo/enterprise#113845 Forward-Port-Of: odoo/enterprise#112041