Odoo Changelog — 2025-08-03

Sunday, August 3, 2025

3 changes · saas-18.4

Bug Fixes(3)

Resolved issues and error corrections

[FIX] sale_{project}: set project company to match the project's partner company

Coresaas-18.4projectsale_projectMedium

Confirming a sales order for a service product could fail when its project template had no company set but the customer did. The fix automatically aligns the generated project with the customer's company, preventing the error and allowing sales orders to be confirmed smoothly.

Original PR description

Currently, a user error occurs when confirming a Sales Order (SO). **Steps to reproduce:** 1) Install sale_project 2) Create a service product that generates a project and a task. 3) Add a project…

Currently, a user error occurs when confirming a Sales Order (SO).

**Steps to reproduce:**

1) Install sale_project
2) Create a service product that generates a project and a task.
3) Add a project template by creating one from the product form view.
4) Create an SO by creating a customer with a company
5) Add the above-created service product and confirm the SO.

**Error:**
A user exception will be triggered
```
The project and the associated partner must be linked to the same company.
```

**Cause:**

- When a project template is created from the product view,
both the customer and the company_id default to empty.

- Later, when confirming a SO with a customer that belongs to a company,
the new project's company_id is taken from the project template, which is empty.

https://github.com/odoo/odoo/blob/876e9d5e9ba87fa69188b2da098eec78f77040f5/addons/sale_project/models/sale_order.py#L140-L141

- However, the project’s partner_id (the customer) does have a company_id,
(since the customer value for the project will be set through SO's customer).

- This leads to a mismatch between the project’s company_id(which is empty)
and its partner’s company_id. So a user exception will be triggered from the below lines

https://github.com/odoo/odoo/blob/876e9d5e9ba87fa69188b2da098eec78f77040f5/addons/project/models/project_project.py#L257-L258

**Solution:**

- If the project template has no company_id, and the customer of the project has one,
set the project’s company_id to match that of the customer.

opw-4900741,4880495

Forward-Port-Of: odoo/odoo#216582

#sales orders#projects#company#customer

[FIX] mail: avoid active domain on missing active field

PR #221664

Coresaas-18.4calendarmailmass_mailing_smsproject_todotest_mail

This change prevents the activity menu from applying an archived-record filter to items that do not support it. It keeps activity lists working correctly across apps while still hiding archived activities where appropriate.

Original PR description

In this forward-port [1]
`active_test=False` is replaced with `[('active', 'in', [True, False])]`
to prevent "active_test" from applying on the activities, which should
not be displayed when archived by default.

The change cannot be applied generically because not all activity mixin
models have an "active" field.

Instead the groups can define their domain depending on their individual
fields. "group domains" are conveniently already supported for use cases
like "fake" groups for todo tasks and the likes.

[1]: https://github.com/odoo/odoo/commit/1cd920a2c7ed251d5e74a890f7183a7620bc06a3

Forward-Port-Of: odoo/odoo#221579

#activities#archived records#activity menu

[FIX] pos_urban_piper: revert commented code

PR #91583

Enterprisesaas-18.4pos_urban_piper

This fix restores code in the Urban Piper point-of-sale integration that had been unintentionally left commented out. It helps ensure the integration keeps working as expected after the previous automated update.

Original PR description

After this commit:
- Code is been restored which was merged in the fw-bot PR

Ref PR : https://github.com/odoo/enterprise/pull/91578/files

#point of sale#Urban Piper#integration

Currently, a user error occurs when confirming a Sales Order (SO). **Steps to reproduce:** 1) Install sale_project 2) Create a service product that generates a project and a task. 3) Add a project template by creating one from the product form view. 4) Create an SO by creating a customer with a company 5) Add the above-created service product and confirm the SO. **Error:** A user exception will be triggered ``` The project and the associated partner must be linked to the same company. ``` **Cause:** - When a project template is created from the product view, both the customer and the company_id default to empty. - Later, when confirming a SO with a customer that belongs to a company, the new project's company_id is taken from the project template, which is empty. https://github.com/odoo/odoo/blob/876e9d5e9ba87fa69188b2da098eec78f77040f5/addons/sale_project/models/sale_order.py#L140-L141 - However, the project’s partner_id (the customer) does have a company_id, (since the customer value for the project will be set through SO's customer). - This leads to a mismatch between the project’s company_id(which is empty) and its partner’s company_id. So a user exception will be triggered from the below lines https://github.com/odoo/odoo/blob/876e9d5e9ba87fa69188b2da098eec78f77040f5/addons/project/models/project_project.py#L257-L258 **Solution:** - If the project template has no company_id, and the customer of the project has one, set the project’s company_id to match that of the customer. opw-4900741,4880495 Forward-Port-Of: odoo/odoo#216582

In this forward-port [1] `active_test=False` is replaced with `[('active', 'in', [True, False])]` to prevent "active_test" from applying on the activities, which should not be displayed when archived by default. The change cannot be applied generically because not all activity mixin models have an "active" field. Instead the groups can define their domain depending on their individual fields. "group domains" are conveniently already supported for use cases like "fake" groups for todo tasks and the likes. [1]: https://github.com/odoo/odoo/commit/1cd920a2c7ed251d5e74a890f7183a7620bc06a3 Forward-Port-Of: odoo/odoo#221579