Wednesday, April 30, 2025
6 changes · 18.0
Resolved issues and error corrections
Long blog post titles now stay within their display area in the Website blog kanban view. This prevents titles from overlapping nearby elements, making the page list easier to read and use.
Original PR description
<b>Steps to reproduce:</b> 1. Install website_blog. 2. Go to Website > Site > Blog Posts > Kanban View. <b>Issue:</b> The titles in the Blog Post Pages are not displaying correctly. When the titles had long text, they overflowed their container boundaries and visually overlapped adjacent UI elements. The text-truncate class was not solving the problem, causing the titles to still overlap. <b>Solution:</b> Fixed the text overflow by applying the d-block class directly to the field element, ensuring proper containment and preventing overlap. opw-4635231
Admin users now have the needed stock lot permission during picking tour tests, ensuring the lot field appears as expected. This prevents an automated stock workflow test from failing and helps keep inventory processes stable.
Original PR description
lot_id was column that needs stock.group_production_lot group to be visible to admin user, so it was not visible in the list view of stock.picking.tour and the tour depends on it visibility build_error-111685
The CRM onboarding tour now keeps its guidance bubble visible until an opportunity is dropped into the correct stage. This helps users complete the guided workflow reliably and avoids confusion when dragging records in the CRM pipeline.
Original PR description
Fix drag and drop in CRM tour because the tour bubble disappear if the record has not been dropped in the correct column. Now the tour bubble will stay visible until the opportunity is dropped in the correct stage. Still taking the last record of first column first, then last of second column, etc ... Task-4624497 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures the Monster recruitment integration depends on the module that provides a required recruitment settings option. It prevents configuration screens from failing when related recruitment extraction services are not installed.
Original PR description
`hr_recruitment_integration_monster` bases one of its view overrides on `<setting id="job_board">`. This element is added by the `hr_recruitment_extract` module, but there is no dependency between the two. `hr_recruitment_integration_monster` only depends on `hr_recruitment_integration_base` which only depends on `hr_recruitment`. `hr_recruitment_extract` depends on `hr_recruitment` but also `iap`, `iap_mail`, and `mail_enterprise`. If any of these last 3 modules is uninstalled, `hr_recruitment_extract` will be uninstalled and the `res_config_settings_view_form` view will explode the first time it gets resolved / validated.
Users can now insert Planning pivot data into spreadsheets without hitting an error when project planning is enabled. This prevents a workflow interruption for teams using planning and timesheet features together.
Original PR description
Currently, an error is raised when users attempt to insert data into a spreadsheet under the following conditions: - Install the modules `timesheet_grid` and `planning`. - Navigate to Planning > Configuration > Settings and enable the `Project Planning` option. - Navigate to Schedule > By Resource > Open Pivot View. - Click on Insert in Spreadsheet. `KeyError: 'effective_hours'` The error occurs because the system attempts to access a missing key `effective_hours` directly with `r[f]` [1], resulting in a KeyError. Link[1]: https://github.com/odoo/enterprise/blob/6d0ee2d7a8141ada362726279bfee77cee937aae/planning/models/planning.py#L723 To resolve this issue, we use `get()` to retrieve the value of the key, ensuring that if the key is missing an error will not occur. sentry-6220456284
The customer statement total now correctly includes both customer invoices and vendor bills for the same partner. This prevents understated or misleading balances when a partner has payable amounts, including on older deprecated accounts.
Original PR description
Steps: - Create a partner P - Create an invoice for 200 and a bill for 100 with P as partner - Go to P form view -> The 'Customer Statement' smart button show 200 instead of 100 This is because the total due does not take into account the accounts of type `liability_payable` in the unreconciled aml domain. With this commit, we adapt the domain to include the good accounts. We also include deprecated accounts. Although it is unlikely to have unreconciled aml from these accounts, it is reflected in the customer statement, so it needs to be computed in the total due. opw-4664402