Daily updates from Odoo
Tuesday, April 7, 2026
18 changes
4 changes
Enhancements to existing features
This update simplifies the process of upselling non-recurring products when the subscription start date aligns with the next invoice date. A technical adjustment was made to prevent errors related to zero prorata ratios, ensuring accurate invoicing and subscription confirmations. This change improves the reliability of the subscription upselling process.
Original PR description
Make easy for module that extend sale subscription to allow for some specific case to upsell subscription with start_date = next_invoice Forward-Port-Of: odoo/enterprise#112730
This update simplifies user database access management by adding a dedicated 'databases' tab to the user view. Previously, administrators had to manually search for user database connections. Now, they can quickly view and manage all databases a user has access to, improving efficiency and security.
Original PR description
The aim of this commit is to allow db_manager to see the list of databases in which a specific user has access and to allow removing this access in bulk if required. Before this commit: To see the list of db in which a user has access, a db_manager would have to go to the list view and make a search on the login/name of the user, potentially matching other db_user in the process. After this commit: The list of db is available out of the box in a databases tab on the res.user view. Task-id: 5945298 Forward-Port-Of: odoo/enterprise#112645
This update improves the setup process for printers in our Point of Sale system. A new checklist document has been added to the POS form, guiding users through the necessary steps to enable LNA access for their printers via the browser. This simplifies the configuration and reduces user frustration.
Original PR description
The LNA configuration for printers is complicated for users. To help them this PR will add a check list document inside the point of sale form view which will explain all the steps the clients should do to enable LNA access for their printers in the browser. Task-[5933321](https://www.odoo.com/odoo/project/1737/tasks/5933321) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#253461 Forward-Port-Of: odoo/odoo#249226
This update adds labels to journal entries that initiate cash basis accounting. This provides clearer traceability, allowing us to understand exactly which transactions led to the creation of cash basis line items. It improves auditability and simplifies reconciliation processes.
Original PR description
To have a more explicit reference from which documents a cash basis base line was created, now we put the name of the two journal entries that triggered the caba. target: 18.0 -> master Task [link](https://www.odoo.com/odoo/project.task/5883344) task-5883344 Forward-Port-Of: odoo/odoo#257795 Forward-Port-Of: odoo/odoo#246610
2 changes
Enhancements to existing features
This update simplifies database access management for users by adding a dedicated 'databases' tab to the user view. Now, administrators can easily see and manage which databases a user has access to, streamlining the process and reducing manual searching.
Original PR description
The aim of this commit is to allow db_manager to see the list of databases in which a specific user has access and to allow removing this access in bulk if required. Before this commit: To see the list of db in which a user has access, a db_manager would have to go to the list view and make a search on the login/name of the user, potentially matching other db_user in the process. After this commit: The list of db is available out of the box in a databases tab on the res.user view. Task-id: 5945298 Forward-Port-Of: odoo/enterprise#112645
This update adds labels to journal entries that initiate cash basis accounting. This provides clearer traceability, allowing us to understand exactly which documents led to the creation of cash basis line items. It improves auditability and simplifies troubleshooting related to cash basis reporting.
Original PR description
To have a more explicit reference from which documents a cash basis base line was created, now we put the name of the two journal entries that triggered the caba. target: 18.0 -> master Task [link](https://www.odoo.com/odoo/project.task/5883344) task-5883344 Forward-Port-Of: odoo/odoo#257795 Forward-Port-Of: odoo/odoo#246610
1 change
Enhancements to existing features
This update adds labels to cash basis journal entries to clearly identify the original documents that triggered them. This improves traceability and simplifies reconciliation processes within the accounting system. The change enhances clarity and auditability for financial reporting.
Original PR description
To have a more explicit reference from which documents a cash basis base line was created, now we put the name of the two journal entries that triggered the caba. target: 18.0 -> master Task [link](https://www.odoo.com/odoo/project.task/5883344) task-5883344 Forward-Port-Of: odoo/odoo#257019 Forward-Port-Of: odoo/odoo#246610
8 changes
Enhancements to existing features
This update clarifies the display of room bookings that span multiple days, making it easier for users to understand the booking duration. Previously, bookings were only shown on the start date, which could be confusing. Now, the booking shows both dates involved, preventing potential issues with editing and ensuring clarity.
Original PR description
Purpose ======= Improve the display of the bookings spanning over multiple days in the room booking sidebar. Specification ============= Currently bookings spanning over multiple days are displayed on their start date. Example: a booking starting on the 1st of January at 2PM and ending on the 2nd of January at 4PM will be displayed: Monday, January 1, 2026 2PM -> 4PM It can be really confusing for users. Improving the display to make it more explicit: Monday, January 1, 2026 - Tuesday, January 2, 2026 2PM -> 4PM Choosing to display the 2 dates instead of spliting the booking into 2 cards (like January 1, 2PM -> Midnight and January 2, Midnight -> 4PM) to make sure users understand it's one single booking and prevent introducing strange behavior when editing the booking start or end (i.e. disappearing cards). Task-5959555
This update improves the spreadsheet edition by introducing dynamic list functions, allowing for more flexible data manipulation within lists. The changes include renaming a key function and generalizing a component for reuse across various spreadsheet data sources, ultimately enhancing user productivity and data analysis capabilities.
This update makes it easier to upsell non-recurring products when the subscription start date aligns with the next invoice date. The change improves the process by separating constraint logic, allowing for greater flexibility and preventing potential errors related to zero prorata ratios during the upsell confirmation.
Original PR description
Make easy for module that extend sale subscription to allow for some specific case to upsell subscription with start_date = next_invoice Forward-Port-Of: odoo/enterprise#112730
This update enhances the payslip search functionality by allowing users to group results by employee type. The search view has been reorganized with a new 'Employee Type' filter and a refined layout for better usability. This change improves reporting and data analysis related to payroll.
Original PR description
Add `employee_type_id` as a stored related field on `hr.payslip` (via `version_id.employee_type_id`) to enable grouping by employee type. Update the payslip search view group by section: - Add "Employee Type" group by filter - Remove "Employee Record" (version_id) group by filter - Rename "Status" to "Payslip Status" - Reorder: Pay Run, Employee, Employee Type, Structure, Payslip Status, Department, Job Position, Company task-6071102
This update enhances the Discuss chat view by displaying the meeting status of participants, indicating if they are currently in a busy or accepted calendar event. This provides clearer context during conversations and helps users understand scheduling availability. Only busy and accepted calendar events are now considered.
Original PR description
Before Changes: - No meeting status was shown in discuss conversations. - Users could not see if the other participant was currently in a meeting. After Changes: - Show 'In a meeting until <time>' with calendar icon in chat view. - Only busy and accepted events are considered. - Private/Confidential and all-day events are ignored. task-3368725
This update enhances the mobile experience by allowing users to quickly access the command palette directly from the home menu. Previously hidden, the search input is now revealed with a swipe, providing a more intuitive and efficient way to find commands on touch devices. This improves usability and productivity for mobile users.
Original PR description
*: web_studio This commit introduces a native-feeling interaction to open the command palette from the home menu on mobile devices. The home menu's search input, which is normally visually hidden, is now rendered on mobile devices but initially hidden underneath the navbar using a scroll offset. Users can intuitively swipe down to reveal the input and tap it to instantly open the command palette. task-5966849
This update simplifies database access management for users within Odoo. Now, a list of databases a user has access to is readily available within the user's profile, eliminating the previous manual search process. This improves efficiency and control over user permissions.
Original PR description
The aim of this commit is to allow db_manager to see the list of databases in which a specific user has access and to allow removing this access in bulk if required. Before this commit: To see the list of db in which a user has access, a db_manager would have to go to the list view and make a search on the login/name of the user, potentially matching other db_user in the process. After this commit: The list of db is available out of the box in a databases tab on the res.user view. Task-id: 5945298 Forward-Port-Of: odoo/enterprise#112645
This update enhances the security and logging around exporting large amounts of data from Odoo spreadsheets. Specifically, it adds logging for common export actions like downloading and printing, and restricts access to frozen/XLSX downloads to authorized users. This improves data tracking and protects sensitive information.
Original PR description
Forward-Port-Of: odoo/enterprise#111405 Forward-Port-Of: odoo/enterprise#85888
3 changes
Enhancements to existing features
This update adds the ability to automatically upload Odoo invoices to FedEx, ensuring accurate export documentation and matching accounting records. It also introduces enhanced shipment tracking with customizable PO numbers, customer references, and invoice numbers for improved visibility. These features are optional and maintain compatibility with existing FedEx shipping configurations.
Original PR description
Add two new configurable options to the FedEx shipping integration: 1. ETD with Odoo Invoice (new documentation_type option): New 'ETD with Odoo Invoice' option in the Generate Invoice setting. When…
Add two new configurable options to the FedEx shipping integration: 1. ETD with Odoo Invoice (new documentation_type option): New 'ETD with Odoo Invoice' option in the Generate Invoice setting. When selected, the module uploads the Odoo-generated invoice PDF to FedEx Documents API (encodedmultiupload endpoint) and references it in the shipment request as an ETD attached document. This replaces the FedEx-generated commercial invoice with the actual Odoo invoice, ensuring export documents match accounting records. Requires a posted invoice on the SO before shipping. Note: FedEx Documents API uses a different base URL (documentapi.prod.fedex.com) than the Ship API. 2. Enhanced References (new Boolean field): When enabled, shipment package references include up to 3 fields: - PO Number: Customer Reference from SO (client_order_ref), or SO number if not set - Customer Reference: SO number - Invoice Number: Odoo posted invoice number When disabled, existing behavior is preserved (PO Number = SO number). Both features are opt-in via carrier configuration fields, preserving full backward compatibility with existing setups.
This update simplifies the user interface by standardizing the term 'Audit Report' to 'Annual Report'. Previously, the inconsistent use of both terms created confusion for users. This change improves clarity and ease of navigation within the accounting knowledge section.
Original PR description
The user interface currently uses both the terms "Audit Report" and "Annual Report", which can be confusing for users. To eliminate this confusion, "Audit Report" will be renamed to "Annual Report". backport of https://github.com/odoo/enterprise/commit/c2fc5a1643f2e005007437f7ae655d2329ac49ad [feeback-6088379](https://www.odoo.com/odoo/project.task/6088379)
This update simplifies user database access management by adding a dedicated 'databases' tab to the res.user view. Previously, administrators had to manually search for user database access, now it's readily available. This improves efficiency and simplifies user permission management.
Original PR description
The aim of this commit is to allow db_manager to see the list of databases in which a specific user has access and to allow removing this access in bulk if required. Before this commit: To see the list of db in which a user has access, a db_manager would have to go to the list view and make a search on the login/name of the user, potentially matching other db_user in the process. After this commit: The list of db is available out of the box in a databases tab on the res.user view. Task-id: 5945298