Odoo Changelog — 2025-09-05

Friday, September 5, 2025

2 changes · master

Refactoring(2)

Code cleanup and technical improvements

[REF] l10n_mx_edi_stock: Use fleet to handle Mx vehicles

Enterprisemasterl10n_mx_edi_stockMEDIUM

Bills of lading for Mexico now use vehicle and driver details from the Fleet app instead of requiring separate vehicle records. This reduces duplicate data entry, keeps vehicle information consistent, and improves weight handling and PDF output for transport documents.

Original PR description

Description of the issue/feature this PR addresses: 
Users that have their own vehicles (the target user for carta porte also does) handle registries of their vehicles in fleet, but with the current implementation the user needs to create the vehicle in both carta porte and fleet making the purpose of fleet redundant.

Current behavior before PR:
The values for the vehicle in the bill of lading are taken from the l10n_mx.vehicle model, which causes users who have fleet records to have duplicate information.

Desired behavior after PR is merged:
The vehicle values on the bill of lading are taken from the fleet.vehicle model. The vehicle driver (driver_id in fleet.vehicle) is taken as the intermediary (driver) on the bill of lading. The computed method of the gross_vehicle_weight field has been reworked so that it is now always in tons. Minor corrections were made to the bill of lading PDF.

opw-[4117145](https://www.odoo.com/odoo/my-tasks/4117145)

I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#mexico#bill-of-lading#fleet#vehicles

[REF] timesheet_grid: review timer header component

PR #81686

Enterprisemasterhelpdesk_timesheetindustry_fsmsale_timesheet_enterpriseMEDIUM

The timesheet timer header was reworked to behave more consistently across list, grid, kanban, Helpdesk, Field Service, and sales timesheet views. This reduces crashes, stale timer displays, and data conflicts when users start, stop, or edit timed work entries.

Original PR description

Before this commit, multiple bug fixes have been made in the timer
header when this component has been mounted in the list view since the
list model conflicts with the one used in timer header component.

This commit completely reviews the timer header component. It also
introduces a new service called timesheet timer service which is the
timer service but with additional data needed for the timer header
component.

task-4284216

#timesheets#timer#helpdesk#field-service#reliability

Description of the issue/feature this PR addresses: Users that have their own vehicles (the target user for carta porte also does) handle registries of their vehicles in fleet, but with the current implementation the user needs to create the vehicle in both carta porte and fleet making the purpose of fleet redundant. Current behavior before PR: The values for the vehicle in the bill of lading are taken from the l10n_mx.vehicle model, which causes users who have fleet records to have duplicate information. Desired behavior after PR is merged: The vehicle values on the bill of lading are taken from the fleet.vehicle model. The vehicle driver (driver_id in fleet.vehicle) is taken as the intermediary (driver) on the bill of lading. The computed method of the gross_vehicle_weight field has been reworked so that it is now always in tons. Minor corrections were made to the bill of lading PDF. opw-[4117145](https://www.odoo.com/odoo/my-tasks/4117145) I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Before this commit, multiple bug fixes have been made in the timer header when this component has been mounted in the list view since the list model conflicts with the one used in timer header component. This commit completely reviews the timer header component. It also introduces a new service called timesheet timer service which is the timer service but with additional data needed for the timer header component. task-4284216