Odoo Changelog — 2026-02-08

Sunday, February 8, 2026

6 changes

Branch: saas-19.1

2 changes

Bug Fixes(2)

Resolved issues and error corrections

[FIX] account: don't block edition of opening date if an opening move is posted

PR #247712

Coresaas-19.1account

This update resolves an issue where users were unable to set the opening date when posting opening moves in the tax returns wizard. The fix ensures the date field is always editable, providing a smoother user experience. This change aligns with the current workflow and maintains compatibility for users accustomed to the previous setup bar flows.

Original PR description

To reproduce the issue (in enterprise):
- Go to accounting > configuration
- click on "Review Manually" (under Accounting Import)
- add a balance to 1 or 2 accounts
- Search for the created draft opening move in the journal entries, and post it
- On the dashboard, click on "Tax returns" ====> The opening date is not set in the wizard, and still, it's not editable. You're stuck

The opening date was originally introduced in the setup bar flows, years ago. Today, this field isn't really used anymore, except for creating the returns, and it then does not especially always correspond to the date of the opening move. To solve the issue, we just always allow editing it in the wizard. To keep things comfortable for users who would be used to the previous way it worked, we still modify the date of the opening move when doing so if it's still in draft.

Forward-Port-Of: odoo/odoo#247676
Forward-Port-Of: odoo/odoo#247606

#accounting#tax returns#opening date

[FIX] appointment: allow apt manager to create appointments from New button

PR #106823

Enterprisesaas-19.1appointmentMEDIUM

This update resolves an issue where appointment managers couldn't create new appointments after removing themselves from a specific appointment type's user list. The fix ensures appointment managers retain their ability to create appointments through the standard 'New' button, improving usability for all users.

Original PR description

Steps to reproduce: ------------------- 1. Go to Appointments and configure an Appointment Type (e.g., Dental care). 2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the…

Steps to reproduce:
-------------------
1. Go to Appointments and configure an Appointment Type (e.g., Dental care).
2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the Users(staff_user_ids) for that type.
3. Click on the "Appointments" stat button
4. Click the "New" button to create a new appointment record.
5. Try to save the record.

Issue:
------
A Validation Error is raised:
```
"Mitchell Admin" cannot be used for "Dental Care"
```
Cause:
-------
After this 5928fda, we support inverse capacity for user appointments. This method
[_inverse_resource_ids_or_capacity](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/calendar_event.py#L355-L360) triggers the method [_check_user_or_resource_match_appointment_type](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/appointment_booking_line.py#L45-L46)
and it will check, appointment_user_id (admin) is not part of the appointment type’s staff_user_ids,
causing a false incompatibility.

**NOTE**:
If we create an appointment by clicking on a slot on the gantt view, it won't cause an issue
as it explicitly updates `user_id` based on `default_partner_ids`. https://github.com/odoo/enterprise/blob/f40e24e67a1664a13acdd01578d8269d084ee421/appointment/models/calendar_event.py#L66-L69

solution:
-----------
Use `has_access` to ensure the current user is allowed to create.

opw-5273175

Forward-Port-Of: odoo/enterprise#101437

#appointments#user permissions

Branch: master

1 change

Bug Fixes(1)

Resolved issues and error corrections

[FIX] appointment: allow apt manager to create appointments from New button

PR #106824

EnterprisemasterappointmentMEDIUM

This update resolves an issue where appointment managers (admins) couldn't create new appointments through the 'New' button. The fix adjusts how access is checked to correctly allow admins to schedule appointments within specific appointment types. This ensures all users can utilize the appointment scheduling functionality.

Original PR description

Steps to reproduce: ------------------- 1. Go to Appointments and configure an Appointment Type (e.g., Dental care). 2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the…

Steps to reproduce:
-------------------
1. Go to Appointments and configure an Appointment Type (e.g., Dental care).
2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the Users(staff_user_ids) for that type.
3. Click on the "Appointments" stat button
4. Click the "New" button to create a new appointment record.
5. Try to save the record.

Issue:
------
A Validation Error is raised:
```
"Mitchell Admin" cannot be used for "Dental Care"
```
Cause:
-------
After this 5928fda, we support inverse capacity for user appointments. This method
[_inverse_resource_ids_or_capacity](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/calendar_event.py#L355-L360) triggers the method [_check_user_or_resource_match_appointment_type](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/appointment_booking_line.py#L45-L46)
and it will check, appointment_user_id (admin) is not part of the appointment type’s staff_user_ids,
causing a false incompatibility.

**NOTE**:
If we create an appointment by clicking on a slot on the gantt view, it won't cause an issue
as it explicitly updates `user_id` based on `default_partner_ids`. https://github.com/odoo/enterprise/blob/f40e24e67a1664a13acdd01578d8269d084ee421/appointment/models/calendar_event.py#L66-L69

solution:
-----------
Use `has_access` to ensure the current user is allowed to create.

opw-5273175

Forward-Port-Of: odoo/enterprise#101437

#appointments#scheduling#admin

Branch: 19.0

2 changes

Improvements(1)

Enhancements to existing features

Master split results dtda next 2 dtda

PR #106825

Enterprise19.0hraccountl10n_hk_hr_payrolll10n_hk_payment_hsbcnetMEDIUM

This PR introduces a new tour to demonstrate overtime ruleset setup and improves pay run validation by restricting access to sensitive actions. It also includes updates to localization reports for HSBCnet payments in Hong Kong, addressing inconsistencies and batch processing.

#payroll#overtime#validation#reports#localization#hsbcnet

Bug Fixes(1)

Resolved issues and error corrections

[FIX] appointment: allow apt manager to create appointments from New button

PR #101437

Enterprise19.0appointmentMEDIUM

This update resolves an issue where appointment managers couldn't create new appointments through the 'New' button. The fix adjusts how access is checked, allowing managers to create appointments as expected. This ensures all users can utilize the appointment scheduling functionality.

Original PR description

Steps to reproduce: ------------------- 1. Go to Appointments and configure an Appointment Type (e.g., Dental care). 2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the…

Steps to reproduce:
-------------------
1. Go to Appointments and configure an Appointment Type (e.g., Dental care).
2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the Users(staff_user_ids) for that type.
3. Click on the "Appointments" stat button
4. Click the "New" button to create a new appointment record.
5. Try to save the record.

Issue:
------
A Validation Error is raised:
```
"Mitchell Admin" cannot be used for "Dental Care"
```
Cause:
-------
After this 5928fda, we support inverse capacity for user appointments. This method
[_inverse_resource_ids_or_capacity](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/calendar_event.py#L355-L360) triggers the method [_check_user_or_resource_match_appointment_type](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/appointment_booking_line.py#L45-L46)
and it will check, appointment_user_id (admin) is not part of the appointment type’s staff_user_ids,
causing a false incompatibility.

**NOTE**:
If we create an appointment by clicking on a slot on the gantt view, it won't cause an issue
as it explicitly updates `user_id` based on `default_partner_ids`. https://github.com/odoo/enterprise/blob/f40e24e67a1664a13acdd01578d8269d084ee421/appointment/models/calendar_event.py#L66-L69

solution:
-----------
Use `has_access` to ensure the current user is allowed to create.

opw-5273175

#appointments#user permissions

Branch: 18.0

1 change

Bug Fixes(1)

Resolved issues and error corrections

[FIX] hr_skills: make skills_tour more reliable

PR #247710

Core18.0hr_skills

This update resolves an issue where a validation error dialog incorrectly closed over another dialog during the skills tour. By ensuring the validation error dialog displays the 'validation error' string, the tour now functions reliably, preventing unexpected behavior and improving the user experience. This fix focuses on the HR_Skills module.

Original PR description

During the skills_tour, a validation error dialog is closed, and this dialog is over another dialog that was being validated.

Before this commit, the close button that was selected was "the one of the not-inactive modal footer", just after a step that was also a click on a button in a modal.

Since the delay between tour steps has been reduced, it happened that the step labeled "Close validation error popup" was executed before the inactivation of the modal, and then the button to be clicked was the one of the underlying modal, because the validation error was not displayed yet.

With this commit, we specifically expect the validation error modal to contain the string "validation error", which makes this issue disappear.

Runbot-build-error: [238886](https://runbot.odoo.com/odoo/runbot.build.error/238886)

#HR#Skills Tour#Validation

To reproduce the issue (in enterprise): - Go to accounting > configuration - click on "Review Manually" (under Accounting Import) - add a balance to 1 or 2 accounts - Search for the created draft opening move in the journal entries, and post it - On the dashboard, click on "Tax returns" ====> The opening date is not set in the wizard, and still, it's not editable. You're stuck The opening date was originally introduced in the setup bar flows, years ago. Today, this field isn't really used anymore, except for creating the returns, and it then does not especially always correspond to the date of the opening move. To solve the issue, we just always allow editing it in the wizard. To keep things comfortable for users who would be used to the previous way it worked, we still modify the date of the opening move when doing so if it's still in draft. Forward-Port-Of: odoo/odoo#247676 Forward-Port-Of: odoo/odoo#247606

Steps to reproduce: ------------------- 1. Go to Appointments and configure an Appointment Type (e.g., Dental care). 2. Remove the admin(apt manager) user (e.g., "Mitchell Admin") from the Users(staff_user_ids) for that type. 3. Click on the "Appointments" stat button 4. Click the "New" button to create a new appointment record. 5. Try to save the record. Issue: ------ A Validation Error is raised: ``` "Mitchell Admin" cannot be used for "Dental Care" ``` Cause: ------- After this 5928fda, we support inverse capacity for user appointments. This method [_inverse_resource_ids_or_capacity](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/calendar_event.py#L355-L360) triggers the method [_check_user_or_resource_match_appointment_type](https://github.com/odoo/enterprise/blob/397de08c3b772228819416d2f5bb80ccda34b795/appointment/models/appointment_booking_line.py#L45-L46) and it will check, appointment_user_id (admin) is not part of the appointment type’s staff_user_ids, causing a false incompatibility. **NOTE**: If we create an appointment by clicking on a slot on the gantt view, it won't cause an issue as it explicitly updates `user_id` based on `default_partner_ids`. https://github.com/odoo/enterprise/blob/f40e24e67a1664a13acdd01578d8269d084ee421/appointment/models/calendar_event.py#L66-L69 solution: ----------- Use `has_access` to ensure the current user is allowed to create. opw-5273175 Forward-Port-Of: odoo/enterprise#101437

During the skills_tour, a validation error dialog is closed, and this dialog is over another dialog that was being validated. Before this commit, the close button that was selected was "the one of the not-inactive modal footer", just after a step that was also a click on a button in a modal. Since the delay between tour steps has been reduced, it happened that the step labeled "Close validation error popup" was executed before the inactivation of the modal, and then the button to be clicked was the one of the underlying modal, because the validation error was not displayed yet. With this commit, we specifically expect the validation error modal to contain the string "validation error", which makes this issue disappear. Runbot-build-error: [238886](https://runbot.odoo.com/odoo/runbot.build.error/238886)