Daily updates from Odoo
Saturday, January 24, 2026
14 changes · master
Enhancements to existing features
This update expands payroll options for Indian businesses, allowing them to use various pay frequencies like daily, weekly, or monthly. Previously, the system was limited to monthly cycles, which is now removed to better accommodate diverse payroll practices and consultant requirements.
Original PR description
Version-master **Purpose**: Currently, many requirements are coming from the consultant side. Several small companies manage payroll on different cycles such as Daily, Weekly, Bi-Weekly, Half-Monthly, Monthly, Quarterly, and Half-Yearly. Therefore, the system should support flexible payslip frequencies to accommodate these varied payroll practices. ### What this PR does - Reintroduces the Wage Type configuration on the employee payroll form. - Allows defining the wage frequency (daily, weekly, bi-weekly, half-monthly, monthly, quarterly, half-yearly, etc.). - Reflects the selected schedule_pay option as a read-only field in salary computation fields, ensuring clarity and consistency in payroll calculations. - Improves usability for consultants and payroll administrators managing multiple payroll cycles. task-5438112
This update expands the availability of the 'Sign' action to several standard company folders, including Employees, Finance, Legal, and Sign. This ensures that users can easily sign documents within these frequently used areas, streamlining document management processes. The change was made to improve consistency and usability across key business areas.
Original PR description
Extend the availability of the Sign embedded action to a set of precreated document folders (Employees, Projects, Finance, Legal, Sign, Admin) and their precreated subfolders. Previously, the Sign action was available only on Inbox and Admin. This update ensures consistent behavior across all relevant predefined folders without affecting user-created folders. ref: [Upgrade PR](https://github.com/odoo/upgrade/pull/9058) task: 5379871
This update allows users to easily share filtered views by copying a URL containing the search criteria. Previously, shared links didn't accurately reflect the user's filters. Now, a new command creates a URL with the current filters, ensuring colleagues see the same search results when they paste the link.
Original PR description
Description of the issue/feature this PR addresses: When teams collaborate, it is often useful to share a page by keeping the searches, (custom) filters and groups. Currently, when the user copies then pastes then URL somewhere, the colleague who clicks on it could not see the same things as the user who shared the link. This can be misleading. Current behavior before PR: The search model does not parse the url query string for search model parameters. Desired behavior after PR is merged: - Command to copy the current filters with the url into the clipboard (from the command pallette) - - > ONLY for stored action, we prevent sharing dynamic actions on purpose. - Activating individual filters / GroupBys from the url params if present. task#5391304 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures accurate accounting for branches with different GST numbers. When a branch is created and its GST number doesn't match the parent company's, separate accounting journals are automatically generated for sales and purchases, aligning with GST regulations and maintaining independent financial records.
Original PR description
Currently, when a branch is created, no separate accounting journals are created by default. As per `Section 25(4) of the CGST Act`, a person having more than one GST registration—whether in the same State/UT or in different States/UTs—is treated as a distinct person under GST law. With this change, the GST number of the branch is compared with that of the parent company at the time of branch creation. If the GST numbers differ, separate accounting journals for `sale` and `purchase` are created for the branch to ensure that independent books of accounts are maintained. task-5417349 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the event track experience by adding the ability to collapse tracks in the list view and significantly improves the agenda view, particularly for multi-day events. Previously, users struggled to manage and view event schedules effectively. This change provides a cleaner and more organized event experience.
Original PR description
Prior to this PR, usability in the `tracks view` and in the `agenda view` was not good. To collapse the tracks, you had to click on the arrow (and only there) There was no collapsing possible in the `agenda view` task-3599197 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves activity views by ensuring users only see activities related to companies they have access to. Previously, users could view activities for companies they weren't connected to, leading to potential confusion. Adding a company ID to activities now correctly associates them with the relevant company record.
Original PR description
Currently, the views "All Activities" and "My Activities" will display every activity belonging to a user, even if they belong to record tied to companies on which the user has no access. This commit adds a company_id fields to activities, which will bind them to the company which own their record, if any. task-4800833
This update automatically installs the Microsoft Outlook module, aligning it with the existing Google Gmail integration. It also addresses a security issue by restricting users from utilizing other users' mail servers, ensuring emails are sent from authorized accounts and preventing unauthorized access.
Resolved issues and error corrections
This update resolves a problem where image transformations were incorrectly applying translations, leading to misaligned images. Removing the translate feature during image transformation ensures accurate resizing and rotation, improving image display quality. The change also updates icons to reflect the removal of translation functionality.
Original PR description
*: `html_builder` In website, the translate feature while transforming an image can occur issues or misleading. This PR aims to remove translate feature from image transformation. task-5190342 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update enhances the portal user experience by automatically scrolling to the specific message when a linked message is opened. Previously, clicking a message link only opened the record, making it harder to quickly view the content. This change improves usability and efficiency for portal users.
Original PR description
*= website_slides, website_sale, test_mail_full **Current behavior before PR:** Opening a copied message link does not automatically scroll to the message for portal users, it only opens the record. **Desired behavior after PR is merged:** Opening the copied link now automatically scrolls to the specific message within the record instead of just opening the record. task-id:[4518058](https://www.odoo.com/odoo/project/1519/tasks/4518058) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update adds a 'Reload Data' button to error dialogs in the Point of Sale system, providing users with a simple way to resolve common issues. This reduces downtime and frustration by allowing quick data recovery, especially for Restaurant orders which now attempt to sync before reloading.
Original PR description
Purpose: ------------ - On Error dialogs, users only had "Ok" or could close the dialog, with no guidance on what to do next. - Many blocking issues are resolved simply by reloading POS data. Before this commit: ----------- - Error dialogs only had an "Ok" button. After this commit: ------------------ - Added a "Reload Data" button for quick recovery of common blocking issues. - Added a warning message in the reload data popup - For POS Restaurant, orders will attempt to sync before reloading data, reducing the risk of data loss. Task-5353590 Forward-Port-Of: odoo/odoo#244321 Forward-Port-Of: odoo/odoo#238112
This update resolves an issue where the map component wasn't displaying correctly within the Odoo Studio. The fix addressed a missing size constraint, allowing the map to render. However, the map remains non-interactive, indicating a separate problem that needs attention.
Original PR description
Before this commit, the map did not render in studio. This was because the container did not have a size. After this commit, the map renders correctly, but it is still not clickable or interactable. task-5432169 Forward-Port-Of: odoo/enterprise#104968 Forward-Port-Of: odoo/enterprise#104114
This update corrects a bug in the Master Production Schedule (MPS) that caused excessive component reordering for kit products. Specifically, a calculation error resulted in the system ordering components in exponential amounts. This fix ensures accurate replenishment and prevents overstocking of components when ordering kits through the MPS.
Original PR description
***Behavior:*** In a setting with a second warehouse that is supplied by the first one. Creating a product that uses that ressuply route, and then adding it to the bom of a kit product will make it…
***Behavior:*** In a setting with a second warehouse that is supplied by the first one. Creating a product that uses that ressuply route, and then adding it to the bom of a kit product will make it so that when ordering the kit product to the second warehouse from the MPS, the system will create an order for an exponential amount of components. When calling action_replenish, kit products for which the components don't have an MPS entry will have their product_ratio computed to know how many components to reorder. However the current formula is wrong or outdated and ends up returning the squared amount. ***Steps to reproduce:*** - Create a second warehouse. - Check Resuply From 'First Warehouse' (this will unarchive a route) - Create a product that uses that route for reordering. - Create a second product - Create a kit for that product BOM composed of the first product make sure the amount of component is more than 1 - In the Master Production Schedule: Add the kit product and make sure it is produced in the second warehouse with the unarchived route. - Add any amount to reorder in 'Replenishment' then click the Order button. - If you go to deliveries and look for your component, you'll see the amount of component per kit squared multiplied by the reordered kit amount. opw-5351460 Forward-Port-Of: odoo/enterprise#101462
Code cleanup and technical improvements
This update consolidates the wishlist and comparison features into the base website sale module, simplifying the codebase and improving maintainability. This change streamlines the eCommerce experience by removing redundant modules and optimizing data processing for product pages.
Original PR description
`website_sale_wishlist` & `website_sale_comparison` were holding the 'Wishlist' & 'Comparison' eCommerce features. In the past, they were optional and installed through the eCommerce settings, since 19.0 they are auto-installed (features are enabled/disabled through the website editor). For code simplification and maintainability, those two features are considered part of a standard eCommerce flow and are now moved into the base `website_sale` module. This allows to remove multiple bridge modules too (and centralize some logic). task-5089613
This update simplifies the process of creating Spanish BOE reports for models 111, 115, and 303. By removing unnecessary encoding and streamlining the generation logic, we've made the process more efficient and easier to maintain, addressing previous issues with complexity and error-proneness.
Original PR description
In Spain, the BOE is a text file generated for each modelo (aka report). It is a .txt file in which the index of the character is the sole indicator of its content. The generation of those text files…
In Spain, the BOE is a text file generated for each modelo (aka report). It is a .txt file in which the index of the character is the sole indicator of its content. The generation of those text files is over-engineered, contains way too much verbose, is error-prone and not change friendly, although the rules tend to change quite often. First, added tests to ensure that the BOE are unaffected by the refactor. Then, simplified the BOE generation for modelos 111, 115 and 303: * Removed the byte-encoding: the only purpose of this was to allow for an easy removal of accentuated characters. This however implied a byte-conversion in every single function. Normalised instead using the character's ascii position. * Added helper functions for common operations (adding X blank spaces, formatting currency...) * United all time-bound legal changes in the beginning of the boe's computation, so legal requirements are clear and isolated, * Streamed the BOE generation in a single simple array. * (+ other minor case-by-case improvement) This is a proof of concept which is why other modelos are yet unaffected. They should be ASAP though ; when it is done, the more complicated functions should be removed. task-5213590