Odoo Changelog — 2025-06-16

Monday, June 16, 2025

3 changes · saas-18.3

Bug Fixes(3)

Resolved issues and error corrections

[FIX] hr_appraisal : allow managers to create appraisal campaigns for their employees

Enterprisesaas-18.3hr_appraisalMEDIUM

Employee managers can now create appraisal campaigns for their own team members even if they do not have broader appraisal access rights. The Launch Campaign button is shown only to managers, helping teams start reviews without needing extra administrative permissions.

Original PR description

Currently, employees managers with no access rights are not allowed to create a new appraisal concern for their employees. To grant managers the access to create appraisal campaigns, new customized access rule for employees' managers has been created. Also, both the Kanban and List views have been modified so that only the managers can see the "Launch Campaign" button.

#appraisals#managers#access rights

[FIX] sign: fix signing document as public user

PR #87769

Enterprisesaas-18.3signMEDIUM

This fixes an issue where people signing a shared document link in a private or public session could not complete the signing flow. The change ensures the system can retrieve the needed signing access details, preventing silent failures and server access errors.

Original PR description

To reproduce:
- As demo user, create a new sign template
- Get the share url and open it in a new private window
- Fill the document fields
- Click on 'Validate and Send Complete Document'
  * enter your name and email
  * click on `Validate and Send` button

Here nothing happen, while on server side an `AccessError` is loggued.

Since https://github.com/odoo/odoo/pull/201565 we need to get new request item access_token as superuser (user who created the template might not the sufficient rights to access it)

#sign#public signing#shared links

[FIX] web_studio: fix error on removal of Default Group By field

PR #86206

Enterprisesaas-18.3web_studio

Fixes an issue in Odoo Studio where clearing the Default Group By field could cause an error and leave the view stuck loading. Users can now remove this setting safely without interrupting their workflow.

Original PR description

A `ValueError` occurs when we set and remove values `Default Group By` in terminal when you click the cross button multiple times the view gets stuck in infinite loading screen.

**Steps to reproduce:**
* Install `web_studio` and `inventory` with demo data
* Inventory>Toggle Studio button>View
* Select any value in `Default Group By` and remove it using cross button.

`ValueError: Invalid field 'None' on model 'stock.picking.type'`

**Solution:**
* The Javascript is passing null value instead we pass an empty string.

**Sentry-6618531530**

#studio#group by#view editor#stability

Currently, employees managers with no access rights are not allowed to create a new appraisal concern for their employees. To grant managers the access to create appraisal campaigns, new customized access rule for employees' managers has been created. Also, both the Kanban and List views have been modified so that only the managers can see the "Launch Campaign" button.

To reproduce: - As demo user, create a new sign template - Get the share url and open it in a new private window - Fill the document fields - Click on 'Validate and Send Complete Document' * enter your name and email * click on `Validate and Send` button Here nothing happen, while on server side an `AccessError` is loggued. Since https://github.com/odoo/odoo/pull/201565 we need to get new request item access_token as superuser (user who created the template might not the sufficient rights to access it)

A `ValueError` occurs when we set and remove values `Default Group By` in terminal when you click the cross button multiple times the view gets stuck in infinite loading screen. **Steps to reproduce:** * Install `web_studio` and `inventory` with demo data * Inventory>Toggle Studio button>View * Select any value in `Default Group By` and remove it using cross button. `ValueError: Invalid field 'None' on model 'stock.picking.type'` **Solution:** * The Javascript is passing null value instead we pass an empty string. **Sentry-6618531530**