Daily updates from Odoo
Navigate
Branch
Saturday, August 23, 2025
13 changes
11 changes
New functionality added to Odoo
The rental flow now supports overnight bookings with defined pickup and return times, making it suitable for hotel-like or nightly rental businesses. Availability calendars and website booking dates now account for those overnight timings so customers see more accurate rental availability.
Original PR description
This PR introduces support for nightly rentals, based on the existing hourly rental unit. Pickup and return times are defined on the Nightly period. This sets the start and end times (hours, minutes) for the rental. The calendar has been adapted to show availabilities, taking into account the pickup time (no red display on day D if the return time is before the next pickup time). task-4477385
Enhancements to existing features
Barcode stock cards now show and highlight more consistently during manufacturing and planned transfers, making it easier for users to see which stock item is being used. The update also reduces confusion by hiding irrelevant destination location details for manufacturing operations and automatically selecting the relevant reserved stock card when possible.
Original PR description
*: barcode, barcode_mrp With this commit ================ - Fixed visibility of quant kanban cards for manufacturing operation types. - Hide the destination location field in the product form view of stock barcode for manufacturing operations. - Implemented CSS styling to highlight the selected kanban card, providing clearer visual feedback to the user. - Quant Cards can be selected if any of the following groups is enabled storage locations, lot/sn, packages, consignment. - Automatically select the quant card associated with a planned transfer by default, indicating the originating quant from which it was reserved. - If any of the move line data is updated manually, if a matching quant exists, its kanban card will be dynamically highlighted. Task: 4551050
VoIP call records no longer store separate provider or company details directly on each call. This streamlines call data management and reduces redundant information, helping keep records cleaner with minimal user-facing impact.
Original PR description
Task-5034202
Newly created subscription-related tasks now take their recurrence settings from the selected task template instead of the sales subscription. This reduces manual edits for users and helps keep recurring field service or project tasks consistent with predefined templates.
Original PR description
Before: ------- Task recurrence values were set based on the sale subscription. After: ----- Task recurrence values are automatically fetched from the task template. Impact: ----- Users no longer need to manually edit the task recurrence values on newly created tasks.this reduces manual effort and saves time. task-4369824
The bank reconciliation widget now shows the complete date, including the year, when users hover over the displayed date. This makes it easier to confirm transaction timing without changing the compact day-and-month view.
Original PR description
Purpose: In bank reconciliation widget, we show only day and month but sometimes you need to know also the year. After this commit: In bank reconciliation widget, the full date(day, month and year) is displayed in a tooltip on hover on the date. task-5030460
Automatic bank reconciliation rules now keep shorter, usable names when similar rules would otherwise receive overly long shared names. Duplicate rule names are handled by adding a number in parentheses, making them easier to identify and manage.
Original PR description
In this commit: https://github.com/odoo/enterprise/commit/e9ab2ae2876970c66c41fa56de70511af24471c1 we change the way the name of automatic reco model are made. But the solution we choose are a bit naive. If the common substring is huge then the reco model is unusable. Since we are stuck with the constraint, the solution we choose is to add a number in parentheses to avoid duplicate. task-5031337 Forward-Port-Of: odoo/enterprise#92992 Forward-Port-Of: odoo/enterprise#92888
Resolved issues and error corrections
Batch payment reconciliation now handles negative bank statement lines, payments without accounting entries, and removal of reconciled payments more reliably. This helps ensure bills are correctly marked as paid and users see accurate available batch payment options during bank reconciliation.
Original PR description
[FIX] account_accountant: batch payment negative statement line When having a negative statement line that we want to reconcile with a batch payment composed with payments from bills. The different…
[FIX] account_accountant: batch payment negative statement line When having a negative statement line that we want to reconcile with a batch payment composed with payments from bills. The different line of the batch payment were not correctly split and so the bills were not put as paid. This was because of the use of the min that in case of negative amount was taking the amount of the entire batch and not the amount of the payment itself. task-4749334 [IMP] account_accountant_batch_payment: payment link and unreconcile When doing a batch payment without entries, the link to the payment was not present since there is no entry link to the aml that we create in the bank rec widget. This commit will add a new many2many field that will be a relation between the move line and the payment so that even when the batch payment has payment without entries we have a link between them This link will also be use for the unreconcile process, when removing a payment from a statement line, we put the payment has in_process and we unreconcile the batch task:4749334 [FIX] account_accountant, account_accountant_batch_payment: batch payment button When selecting or deleting a batch payment, the button was not updated correctly. For example, having just one batch and selecting it should make the button disappear for every statement line. Also, the amount of the batch was wrong since it was not the residual amount. To fix this, we move the logic of to get the different batch payment to the service and use that to update the available batch payment when selecting one or deleting one. task-4749334
After downloading the ADEME database in ESG, users are now taken directly to the emissions factors page instead of remaining on the database page. This makes the workflow clearer and adds logging to help monitor how long ADEME data retrieval takes.
Original PR description
Steps to reproduce: - go on configuration -> databases in ESG - download the ademe database What's happening: A success message is displayed, but the user stays on the database page. What's expected: The user is redirected towards the factor emissions page Additional fix: Small addition of an extra logger in the ADEME download process to allow checking the time needed to fetch the data from the ADEME website Task [link](https://www.odoo.com/odoo/project/967/tasks/4751902) task-4751902 Forward-Port-Of: odoo/enterprise#87058
Users can now clear the partner from a bank statement line after setting an account and editing the line. This fixes a small but visible accounting workflow issue, helping prevent incorrect partner details from remaining on transactions.
Original PR description
Before this commit when doing a set account on a bank statement line, and then editing this line to remove the partner was not working. This commit will allow the user to remove the partner when editing the line. task-4984569 Forward-Port-Of: odoo/enterprise#91422
Portal users can now group helpdesk tickets by customer without running into an access error. This keeps the ticket portal usable for invited customers while respecting existing customer data access limits.
Original PR description
**Issue:**
When logged in as a portal user, grouping tickets by 'Customer' raises an
access error, as portal user can only read partner records if:
```
[('id', 'child_of', user.commercial_partner_id.id)]
```
As defined in rule here:
https://github.com/odoo/odoo/blob/68a156030c366fbbf6b0841e1e2688a571355bf2/odoo/addons/base/security/base_security.xml#L22-L30
**Steps to reproduce:**
- Navigate a helpdesk team and set tickets to be visible to Invited portal
users and all internal users.
- Add a portal user as a follower to one of the team's tickets.
- Log in as the portal user, navigate to Tickets, and group by Customer.
An access error is raised
opw-4969684
Forward-Port-Of: odoo/enterprise#92985
Forward-Port-Of: odoo/enterprise#92603Belgian payroll exports now check required work entry codes before generating files, so users get a clear warning instead of a failed export. This helps payroll teams identify missing setup details earlier across supported payroll providers.
Original PR description
Before this commit no usererror was raised when the work entry type has no group s code defined which caused the export to fail. This commit adds a check at generation time for the work entry type to have a group s code defined task-4241431 Forward-Port-Of: odoo/enterprise#92595 Forward-Port-Of: odoo/enterprise#71454
2 changes
Resolved issues and error corrections
This fixes an issue where translated field values could be accidentally cleared when switching languages on unsaved records. It helps users working in multiple languages keep product and other translated data consistent while creating or editing records.
Original PR description
Steps to reproduce the issue:
1. Install a second language (eg, ar_001) and `product`
2. Start odoo shell
3. Run the following:
`(env := env(context=dict(env.context,lang='ar_001')))['product.template'].new({'name':'test'}).with_context(lang='en_US').name`
Current behavior before PR:
The `get` method of the cache will not find a value for the `en_US` language and set the value stored in the env language to a default (`None` in this case) after raising `CacheMiss`
Desired behavior after PR is merged:
We can read and write translatable fields in different languages on transient records without data loss.
opw-4943458
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#222474Vendor bills without taxes are now excluded from GSTR2B reconciliation. This prevents bills that were likely not filed by the vendor from appearing in the reconciliation process, improving report accuracy for Indian GST compliance.
Original PR description
Before this commit- We included the Vendor bills without taxes for GSTR2B reconciliation After this commit- We exclude the Vendor bills without taxes for GSTR2B Because if no tax is there on the bill it means wasn't filed by the Vendor as well task-5023013 Forward-Port-Of: odoo/enterprise#92866