Odoo Changelog — 2025-07-13

Sunday, July 13, 2025

2 changes

Bug Fixes(2)

Resolved issues and error corrections

[FIX] hr_attendance: compute extra hours at creation

Coresaas-18.4hr_attendanceMEDIUM

This fixes an issue where newly created, automatically validated attendance records could show zero extra hours even when an employee worked longer than expected. The correction ensures overtime is calculated immediately when the record is saved, giving HR and payroll users accurate attendance information from the start.

Original PR description

Introduced by cc81bb59f87540cf4dd8da65510417d8023ef65b

**Steps to reproduce**
1. Create a new automatically validated attendance.
2. Set the employee, check in and check fields before saving the form.
Issue: the "Extra hours" field is not computed. e.g.: if the employee has worked 1 hour more than expected, "Worked Extra Hours" equals 1:00 (ok), but "Extra hours" appears as 0:00.

**Cause**
The previous fix intended to avoid recomputation of the `validated_overtime_hours` field. No better way was found than to exclude records where the `overtime_hours` was different than the `validated_overtime_hours` (meaning it had been manually modified by the user).
The problem comes from the fact that at creation,
`validated_overtime_hours` was sent in the `vals_list` to the create with a value of 0.

**Solution**
Force the computation of the field at creation.

Forward-Port-Of: odoo/odoo#217967

#attendance#overtime#payroll

[FIX] marketing_card: translate the timezone of date fields

PR #218730

Coresaas-18.4mailmarketing_cardwebsite_event_trackMEDIUM

Marketing cards now display date and time fields using the timezone that is relevant to the underlying record, such as an event's local timezone, instead of defaulting to UTC. This makes shared cards clearer and prevents recipients from seeing misleading event or schedule times.

Original PR description

When possible we want to fetch a date field in its relevant timezone
not in UTC. As that is generally what you want people to share.

task-4936298

Forward-Port-Of: odoo/odoo#218721
Forward-Port-Of: odoo/odoo#218633

#timezone#dates#marketing cards#events

Introduced by cc81bb59f87540cf4dd8da65510417d8023ef65b **Steps to reproduce** 1. Create a new automatically validated attendance. 2. Set the employee, check in and check fields before saving the form. Issue: the "Extra hours" field is not computed. e.g.: if the employee has worked 1 hour more than expected, "Worked Extra Hours" equals 1:00 (ok), but "Extra hours" appears as 0:00. **Cause** The previous fix intended to avoid recomputation of the `validated_overtime_hours` field. No better way was found than to exclude records where the `overtime_hours` was different than the `validated_overtime_hours` (meaning it had been manually modified by the user). The problem comes from the fact that at creation, `validated_overtime_hours` was sent in the `vals_list` to the create with a value of 0. **Solution** Force the computation of the field at creation. Forward-Port-Of: odoo/odoo#217967

When possible we want to fetch a date field in its relevant timezone not in UTC. As that is generally what you want people to share. task-4936298 Forward-Port-Of: odoo/odoo#218721 Forward-Port-Of: odoo/odoo#218633