Odoo Changelog — 2026-02-08

Sunday, February 8, 2026

2 changes · 19.0

Improvements(1)

Enhancements to existing features

Master split results dtda next 2 dtda

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

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