Wednesday, April 16, 2025
13 changes
10 changes
Enhancements to existing features
Fiduciaries can now revoke Codabox connections even when they no longer have access to the client company's database. This helps prevent former clients from continuing to retrieve bank statements through the fiduciary's Codabox account.
Original PR description
### Before Codabox connections could only be revoked within the company's db, so if the fiduciary didn't have access to their db anymore they wouldn't be able to revoke the connection and the company would still be able to retrieve their statements through the fiduciary's Codabox account. ### Now A new revocation wizard allows for an editable company id field which then allows fiduciaries to revoke connections for companies' whose dbs they can't access anymore using the fiduciary password. odoo/iap-apps/pull/1012 task-4075805
Businesses can now sell partnership products that automatically assign commission plans to customers. The update also supports recurring memberships through subscriptions, making ongoing affiliate or partner relationships easier to manage.
Original PR description
task-4421310
The point-of-sale IoT customer display is now always enabled, so users no longer encounter an unnecessary configuration error. This reduces setup friction and makes the customer display behavior more predictable for stores.
Original PR description
In this commit: ================ Customer display configuration has been removed from res config settings and is always enabled, the user error is no longer needed and has been removed. Task-4604770 Related Community PR:https://github.com/odoo/odoo/pull/201637 Related Upgrade PR:https://github.com/odoo/upgrade/pull/7386
Users can now update a company’s shared address, VAT, and pricelist directly from a related contact, reducing extra navigation and avoiding inconsistent contact data. The change also removes the rarely used follow-up contact type in favor of invoice contacts, making customer records simpler to understand.
Original PR description
Rationale When you edit the contact of a company, you actually edit the company at least for what concerns the address. Specifications for address ==================== Previously fields were readonly…
Rationale When you edit the contact of a company, you actually edit the company at least for what concerns the address. Specifications for address ==================== Previously fields were readonly on form view and people had to follow the m2o to edit it. However this is not really user friendly and also eases desynchronization between code (that does not prevent updating contact address) and interface (who does it). We now consider contacts and their parent share the same address. Synchronization is therefore done upstream. There are still some limitations, like: address is not propagated through the whole contact tree, all descendants are not necessarily always updated, ... This would require a more in-depth rewrite of the sync code. Maybe for later. A new 'type address label' field is added that dynamically updated the partner address label. That way we know we are editing the Company Address when editing a contact. For other types the label indicates it is a specific address (Invoice Address, Delivery, ...) Varia This notably fixes an issue when setting a parent on a contact partner. Previously this parent was a company without address, and the address on the contact was not editable (readonly due to parent). Now it is correctly propagated to the parent. This allows to remove a custom call to '_handle_first_contact_creation' which was updating parent company when setting their first contact child. This is now standard. Method is kept for optimized import that is not touched in this PR to avoid adding performance issues. Vat / Pricelist ========== As for address fields, we now allow to edit VAT and pricelist on partners that are children of companies. It directly edits company, instead of forcing users to go to the parent and edit VAT. Implementation choice is to make a subset of commercial fields, limiting the sync currently on VAT only. Other commercial fields still behave like before this PR, notably to limit side effects, and because VAT is a more commonly updated fields than l10n or reference commercial fields. Varia This fixes an issue when a new parent without values is set on a contact child. Previously to this commit, commercial sync erased child values, which is annoying. Now child is not erased anymore and their values are sent to the parent, which is cool. This is still limited to "synced" values, aka VAT only. Task-4708358 Part of Task-4377720
The product version field in PLM has been repositioned into the traceability section of the product form. This makes version information easier to find alongside related tracking details, improving clarity for manufacturing and product lifecycle users.
Original PR description
Task-4441066
The website generator has been updated to stay compatible with recent changes in the main Odoo website platform. This helps ensure the website setup experience continues to work smoothly for users as the broader system evolves.
Original PR description
See also: - https://github.com/odoo/odoo/pull/201410
Point of Sale users can now view and settle a customer's unpaid invoices during checkout. This makes it easier to collect outstanding balances in-store and gives staff clearer visibility by separating invoice amounts due from order amounts due.
Original PR description
- Added functionality to list and settle unpaid invoices in PoS. - Introduced a "Settle Invoice" product for processing invoice order line. - Enhanced customer balance tracking by distinguishing order due and invoice due amounts. - Add access rights for PoS users to read account.move community PR: https://github.com/odoo/odoo/pull/203672 task-id: 4501448
The spreadsheet test setup no longer loads chart resources that are already included automatically. This reduces duplicated test preparation work and helps keep internal testing simpler without changing business features.
Original PR description
In the helper `prepareWebClientForSpreadsheet`, we would explicitely load some ChartJs assets to ensure their presence but those are already loaded in the tests assets bundle (the test loads spreadsheet.o_spreadsheet which in turn depends on web.chartjs_lib).
Gantt popovers now reuse the existing Kanban-style card view and correctly carry the action context, so fields display or hide as expected. This makes scheduling popovers clearer and more consistent, with warning details such as time off and overlaps shown directly where users review planning items.
Original PR description
Timesheet grids now keep their color indicators when entries are grouped by employee. This makes grouped timesheet views easier to scan and helps users spot important differences or statuses more quickly.
Original PR description
Before this commit there was no color indication on timesheets when grouped by employees. Now color indication is done when grouped by also. task-4653902
3 changes
Enhancements to existing features
The website editor's video-focused editing experience now includes fields for a video title and description. This helps teams provide clearer context for embedded videos and improve the quality of published website content.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1) web_gantt: pass the action context
- Issue:
When the Kanban view is opened from the Gantt popover, the context
is not being passed in the record.If the visibility of the field is
based on the context, it will not work, as shown in the example below.
- For example:
When a task is opened from a specific project, the project name should not be displayed.
- xml:
`<field invisible="context.get('default_project_id', False)" name="project_id" options="{'no_open': True}"/>`
2) In this commit:
- We have used the existing Kanban view in the Gantt popover.
- Time-off, overlapping, and other warnings have been added to the Gantt popover's Kanban view.
task-4444660This pull request adds and updates themes in the staging environment so they can be tested and reviewed before production use. It also includes setup for the apps bar add-on and deployment workflow changes, helping validate visual and configuration compatibility early.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects a typo in the Jordan electronic invoicing module. It is a small quality improvement that helps keep labels or messages clear and professional without changing business workflows.
Original PR description
No task ID.