Odoo Changelog — 2025-06-09

Monday, June 9, 2025

3 changes

Bug Fixes(3)

Resolved issues and error corrections

[FIX] point_of_sale: number buffer when pressing +/-

Core18.0point_of_salepos_loyaltyMEDIUM

This fixes an issue in Point of Sale where using the +/- button on a product quantity or price changed the value to 0 instead of making it negative. Cashiers can now correctly enter negative quantities or prices when needed, reducing checkout errors and manual corrections.

Original PR description

Before this commit
===============
Previously, when adding a product and clicking the "+/-" button, the quantity and price would change to "0" instead of becoming negative.

After this commit
=============
After implementing this commit, pressing the +/- button now results in the quantity and price value changing to negative instead of changing it to 0.

task- 3869556

#point of sale#quantity#pricing#checkout

[FIX] resource: flexible leaves timesheeting as 4 hours

PR #212808

Core18.0resourceMEDIUM

Employees on flexible working calendars can now record time off for the exact number of hours requested. This prevents timesheets linked to time off from incorrectly showing every hourly request as 4 hours, improving payroll and project tracking accuracy.

Original PR description

WIP: This change allows an employee on a flexible working calendar to request time off for any number of hours, and have that time off show up as an equivalent amount of hours on the timesheet.

Before this change, any time off that was requested in hours would show up as 4 hours on the associated project timesheet for that time off type.

Steps to reproduce:
- Using a time off type that is associated with
  a project timesheet, create a time off request
  for 2 hours for an employee on a flexible
  working schedule.
- Approve this time off request and see that
  on this employees timesheet, there is an entry
  for 4 hours, instead of 2.
- You can repeat this test for any amount of hours
  and see that the timesheet entry is always 4
  hours.

opw-4745945

#time off#timesheets#flexible schedule

[IMP] mrp_subcontracting: fallback to supplier when quantity doesn't match

PR #213503

Core18.0mrp_subcontractingMEDIUM

BOM cost reports now include subcontracting costs even when the requested quantity does not match a supplier's minimum quantity exactly. This makes manufacturing cost reports more complete and consistent, helping users avoid missing subcontracting expenses in planning and analysis.

Original PR description

Description of the issue/feature this PR addresses:

When visualizing the structure of a BOM with subcontracted components, the subcontracting cost is omitted if no supplierinfo record exists with a `min_qty` less than or equal to the requested quantity.

This leads to an inconsistent experience compared to regular components, which still show a price by selecting the closest lower `min_qty`. For subcontracted components, if the requested quantity does not match any valid `supplierinfo`, the cost line silently disappears from the report.

Current behavior before PR:

The subcontracting cost is not shown in the BOM cost structure if no `supplierinfo` matches the requested quantity (i.e., `min_qty > quantity`).

Desired behavior after PR is merged:

If no matching supplier is found for the requested quantity, the fallback logic uses any available supplierinfo (as already done in `_format_route_info`), ensuring a price is shown for subcontracted lines. This guarantees the BOM cost structure always includes the subcontracting cost, making the report complete and coherent.

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

#subcontracting#BOM#costing#supplier pricing

Before this commit =============== Previously, when adding a product and clicking the "+/-" button, the quantity and price would change to "0" instead of becoming negative. After this commit ============= After implementing this commit, pressing the +/- button now results in the quantity and price value changing to negative instead of changing it to 0. task- 3869556

WIP: This change allows an employee on a flexible working calendar to request time off for any number of hours, and have that time off show up as an equivalent amount of hours on the timesheet. Before this change, any time off that was requested in hours would show up as 4 hours on the associated project timesheet for that time off type. Steps to reproduce: - Using a time off type that is associated with a project timesheet, create a time off request for 2 hours for an employee on a flexible working schedule. - Approve this time off request and see that on this employees timesheet, there is an entry for 4 hours, instead of 2. - You can repeat this test for any amount of hours and see that the timesheet entry is always 4 hours. opw-4745945

Description of the issue/feature this PR addresses: When visualizing the structure of a BOM with subcontracted components, the subcontracting cost is omitted if no supplierinfo record exists with a `min_qty` less than or equal to the requested quantity. This leads to an inconsistent experience compared to regular components, which still show a price by selecting the closest lower `min_qty`. For subcontracted components, if the requested quantity does not match any valid `supplierinfo`, the cost line silently disappears from the report. Current behavior before PR: The subcontracting cost is not shown in the BOM cost structure if no `supplierinfo` matches the requested quantity (i.e., `min_qty > quantity`). Desired behavior after PR is merged: If no matching supplier is found for the requested quantity, the fallback logic uses any available supplierinfo (as already done in `_format_route_info`), ensuring a price is shown for subcontracted lines. This guarantees the BOM cost structure always includes the subcontracting cost, making the report complete and coherent. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr