Odoo Changelog — 2026-05-21

Thursday, May 21, 2026

4 changes · saas-18.3

Bug Fixes(4)

Resolved issues and error corrections

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

Enterprisesaas-18.3mrp_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 and prevents potential data inconsistencies.

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

#production planning#forecast#data integrity

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

PR #117838

Enterprisesaas-18.3helpdesk

This update fixes an error that occurred when users tried to create new Helpdesk teams. The issue stemmed from attempting to access a missing email template, causing a system crash. The fix 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

[FIX] base: reduce maximal precision when using min_precision

PR #265637

Coresaas-18.3base

This update corrects a minor formatting issue where invoices were displaying extra decimal places in PDF reports. The fix reduces unnecessary precision calculations during invoice printing, ensuring invoices display correctly with the intended number of decimal places. This improves the overall presentation of invoices.

Original PR description

Issue:
- Create an invoice with a line having a price of `528,000,000.00`
- Print the invoice
-> pdf displays `528,000,000.000001`

Cause:
In `value_to_html` from `ir.qweb.field.float`, we compute the maximum
precision that we can get from the value, to avoid parasite digits.
The maximum is 15, so if a number has 11 digits, we won't ask for
a precision higher than 4.
But in `float_round`, they multiple the value with its precision, then
add `epsilon` (a small value).
So we're now working with a 16 digits float, which is what we want to
avoid.

Solution:
Reduce the maximum precision from one digit before calling
`float_round`.

opw-6012129

Forward-Port-Of: odoo/odoo#260955

#invoice#formatting#precision

[FIX] point_of_sale: fix message badge persisting after note removal

PR #265652

Coresaas-18.3point_of_sale

A bug was causing a notification badge to remain visible after a general note was removed from the Point of Sale (POS) system. This update corrects a technical issue where removing a note incorrectly signaled a change, leading to the badge persisting. The fix ensures the badge disappears correctly when a note is deleted.

Original PR description

Steps to reproduce:
-----------
- Open POS Restaurant
- Add a General Note
- Remove the General Note
- The message badge on “Send to Kitchen” remains visible

Issue:
-----------
Removing a General Note set `general_note` to `undefined`, which was
detected as a change and kept the badge visible.

Fix:
--------------
Normalize empty General Notes to an empty string ("") so removing a note
restores the correct initial state.

Task-6101501
Related PR: odoo/enterprise#113514

Forward-Port-Of: odoo/odoo#264730
Forward-Port-Of: odoo/odoo#258632

#pos#bug#notification

## 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: - Create an invoice with a line having a price of `528,000,000.00` - Print the invoice -> pdf displays `528,000,000.000001` Cause: In `value_to_html` from `ir.qweb.field.float`, we compute the maximum precision that we can get from the value, to avoid parasite digits. The maximum is 15, so if a number has 11 digits, we won't ask for a precision higher than 4. But in `float_round`, they multiple the value with its precision, then add `epsilon` (a small value). So we're now working with a 16 digits float, which is what we want to avoid. Solution: Reduce the maximum precision from one digit before calling `float_round`. opw-6012129 Forward-Port-Of: odoo/odoo#260955

Steps to reproduce: ----------- - Open POS Restaurant - Add a General Note - Remove the General Note - The message badge on “Send to Kitchen” remains visible Issue: ----------- Removing a General Note set `general_note` to `undefined`, which was detected as a change and kept the badge visible. Fix: -------------- Normalize empty General Notes to an empty string ("") so removing a note restores the correct initial state. Task-6101501 Related PR: odoo/enterprise#113514 Forward-Port-Of: odoo/odoo#264730 Forward-Port-Of: odoo/odoo#258632