Friday, March 28, 2025
9 changes
2 changes
Resolved issues and error corrections
This fixes spreadsheet filter side panels so they continue to open and collapse correctly after an internal naming change. It helps avoid small interface issues when users edit global filters in spreadsheets.
Original PR description
`collapsedAtInit` has been renamed to `isInitiallyCollapsed`
This fix makes an automated rental checkout test update date inputs more reliably. It helps prevent intermittent build warnings, improving confidence in release checks without changing the customer-facing shopping experience.
Original PR description
Before this commit, we had a non-deterministic warning on some runbot builds: see "shop_buy_rental_product" tour. This is because we set the new value via the daterange picker and we need to trigger an "enter" event to force an input update. runbot error: 161483 Related PR #82005
7 changes
Resolved issues and error corrections
Creating a new Point of Sale payment method no longer fails when the company setup is missing a default outstanding payment account. This prevents an unexpected error during configuration and helps businesses complete POS setup more reliably.
Original PR description
Fix issue when trying to create new payment methods and no `account_journal_payment_debit_account_id` exist in the current chart template.
Calling `_get_outstanding_account('inbound')` on an empty `account.payment` was failing because `self.env.company` was not properly set. This issue only occurred when the outstanding account was not found in the chart template, leading to an exception.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prWhen a bill of materials is created from a manufacturing order linked to a project, it now keeps that project information automatically. This prevents missing project links and helps teams keep manufacturing and project tracking aligned.
Original PR description
Backport of this commit: https://github.com/odoo/odoo/commit/eaf2ea619644c29c9fbccd5410db77053b82d64d
Steps to reproduce the bug:
- Create a storable product “P1”
- Create a MO:
- Product to produce: P1
- Project: set any project
- Save
- Click on the “Generate BoM” button or try to create a BoM directly from the BoM field
- Open the BoM
Problem:
The project field is not inherited from the MO.
opw-4669529This fix makes the HTML editor’s automated tests more reliable by targeting the correct page elements and safely handling images that are still loading when an editor component closes. It helps prevent false test failures and tracebacks in Odoo’s validation system, improving release confidence without changing user-facing behavior.
Original PR description
**Problem**: Tests introduced in commit [`b7a63f7d60494c65889ba6ce3fa18847a0abbb62`] (https://github.com/odoo/odoo/commit/b7a63f7d60494c65889ba6ce3fa18847a0abbb62) are failing on **runbot** due to improper element selection and handling of image loading when the component is destroyed. **Solution**: - Ensure the test properly targets the correct elements. - Handle cases where the image is still loading while the component is destroyed, preventing potential tracebacks. **Steps to Reproduce**: 1. Run the test suite on runbot. 2. Observe test failures related to incorrect element selection or missing image references due to component destruction. **opw-4607020** --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue in the HTML editor where pasting different list types together could convert them all to the same style. This helps users preserve formatting, such as standard lists and checklists, when copying content into Odoo.
Original PR description
**Problem**:
When pasting lists of different types (`UL` and `CL`), a new list is created with all `li` elements matching the type of the first list.
**Solution**:
If `nodeToInsert` is a list element, use its `mode` to create the list instead of using the `mode` of
the container.
**Steps to reproduce**:
1. Copy two lists: ```html <ul><li>1</li></ul> <ul class="o_checklist"><li>1</li><li>2</li><li>3</li></ul> ```
2. Paste into the editor.
Issue: The second list is pasted using the same
type as the first list.
opw-4670379
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis fix ensures the quantity field remains visible when creating manufacturing orders, even at high browser zoom levels or different screen resolutions. Users can reliably enter production quantities without the unit of measure field pushing it out of view.
Original PR description
Steps to reproduce: - Install manfacturing app - Activate the Unit of measure setting in the mrp settings - Go to create new manafcturing order and start zooming in with different screen resolutions…
Steps to reproduce: - Install manfacturing app - Activate the Unit of measure setting in the mrp settings - Go to create new manafcturing order and start zooming in with different screen resolutions Problem: The product_qty field starts disappearing on zooming in and this makes the user can't enter a value in it. This happens because the width:auto applied to the field of the uom beside it that takes as much space as possible so the product_qty field disappears. opw-4560205 Description of the issue/feature this PR addresses: Current behavior before PR: the product_qty field in the creating manufacturing order disappears while zooming in with different screen resolutions. Desired behavior after PR is merged: The product_qty field is appearing on all zoom levels from 100 to 400 and tested on all screen resolutions in the settings of display in Ubuntu **Before**:  **After**:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Updating the allocation amount on a time-off allocation record without an assigned employee no longer triggers an error. This prevents interruptions for HR users when reviewing or editing incomplete allocation records.
Original PR description
An error occurs when updating the **Allocation** field in a time-off allocation record that does not have an assigned employee. **Steps to reproduce:** - Install the `hr_holidays` module. - Navigate to `Time Off > Management > Allocations` (form view). - Remove the employee and modify the **Allocation** field. - Observe the error. **Error:** KeyError - False The issue occurs because `_compute_number_of_hours_display` depends on `employee_id._get_hours_per_day(allocation.date_from)`, when `employee_id` is empty, attempting to access `self.id` at [1] results in a key error. [1] - https://github.com/odoo/odoo/blob/51097d978a698fa94d021ca72bcd69c24d9c768b/addons/hr_holidays/models/hr_employee.py#L349 This commit ensures that the computation of `number_of_hours_display` checks if `employee_id` exists before proceeding. If no employee is assigned, it will be skipped. Sentry - 6423050142
The barcode app now shows product expiration dates immediately when a package is scanned. This helps warehouse users see shelf-life information right away without needing to open or save the line first.
Original PR description
When scanning a package, its content is added on the view, but we don't display the expiration date. To reproduce the issue: 1. In Settings, enable: - Packages - Expiration dates 2. Create a product - Tracked by lot - Expiration date 3. Update its quantity - Lot L - Package P - Quantity > 0 4. Set an expiration date on L 5. Open a new delivery through the barcode app 6. Scan P "Error": a line is added for the product, with its lot L, but we don't display the expiration date. Once the line is saved (for instance, through the edit button), we will finally display it. This is because we don't provide any information about the expiration date when converting the package quant into relevant data. OPW-4516410