Daily updates from Odoo
Navigate
Branch
Sunday, January 11, 2026
24 changes
4 changes
Resolved issues and error corrections
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in duplicate preparation tickets being printed. The fix ensures that preparation tickets are printed only once, regardless of the number of open POS sessions, improving order processing efficiency and reducing printing costs. It also cleans up local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103906 Forward-Port-Of: odoo/enterprise#100280
This update fixes a UI issue where long email messages would overflow their display bubbles, causing a broken user experience. The change makes email content scrollable within the message bubble, ensuring all information is visible and the interface remains functional.
Original PR description
Current behavior before PR: When the email template (message_type = `comment`) has content that is longer (in width), the content tends to overflow out of the bubble which breaks the UI. Desired behavior after PR is merged: This commit fixes the issue by making the content scrollable inside the bubble. Task-5363388 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243034 Forward-Port-Of: odoo/odoo#237878
This update ensures payslips accurately reflect employee data for previous years, resolving an issue where only current year snapshots were updated. The change allows for retroactive updates of payslip years, enabling correct pay calculations and reporting for historical data. This improves payroll accuracy and compliance.
Original PR description
Currently employee data only updates current year snapshots, which can be an issue when generating payslips for previous years, in this PR we enable retroactive updates by changing the mecanism. The new mecanism updates snapshots of the payslip years, making a reference date usage possible. Forward-Port-Of: odoo/enterprise#103386 Forward-Port-Of: odoo/enterprise#103147
This update corrects a display issue where subscription delivery periods (e.g., 'Every Month') were shown in English instead of the user's selected language. The team leveraged existing translation mappings to ensure consistent, localized text on the website for subscription products. Further improvements are planned in the main branch.
Original PR description
This commit[^1] introduced a "Deliver Every [period]" text on the website for subscription consumable products, but used the raw selection key that was not translated. As a result, people would see only the "Deliver Every" part in their language, and the period in English. To fix this in stable, we used the already existing translation mapping for billing periods to also translate the delivery period on the website. In master, we can improve this further by using a computed field with a properly translatable string. Issue reported by support. [^1]: https://github.com/odoo/enterprise/commit/beb7238882eda1fd36aa22bdb6441b8bd5556ef3 Forward-Port-Of: odoo/enterprise#103645
1 change
Resolved issues and error corrections
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in duplicate preparation tickets being printed. The fix ensures that preparation tickets are printed only once, regardless of the number of active POS sessions, streamlining order fulfillment and reducing printing costs. It also cleans up local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103894 Forward-Port-Of: odoo/enterprise#100280
4 changes
Enhancements to existing features
This update addresses flickering and scrolling issues when using the keypad in the voip module, creating a smoother and more intuitive input experience. It also simplifies the long-press implementation and fixes a visual glitch in Firefox, ensuring consistent behavior across browsers.
Original PR description
Before this, there were two weird behaviors when using the keypad buttons to add numbers into the input field: - On each click, the input is visually blurred then focused again, which creates a…
Before this, there were two weird behaviors when using the keypad buttons to add numbers into the input field: - On each click, the input is visually blurred then focused again, which creates a flickering effect of the bottom border. - When the input is full and numbers keep being added, between mousedown and mouseup, the input is scrolled back to the beginning and then scrolled back to the end where the number is added (at least if using Chrome). This seems to be the case at least since [1], even though the input was quite different at the time. Both behaviors are first caused by the same thing: the input being blurred on click. This is now prevented by preventing the default behavior of the buttons pointerdown. After that, the second problem was not entirely fixed: now the scroll of the input never changed, meaning that numbers added "at the end" were not visible as the scroll stayed in place. The cursor is now forced back into view by blurring and focusing again immediately. This simulates nearly the same behavior as using a real keyboard. The only (found) difference is that if the cursor is in the middle when adding a number, and the scroll is not at the start, the cursor stays visually in position as more characters are added. This is judged acceptable (also this is only the case on Chrome). [1]: https://github.com/odoo/enterprise/commit/52b3065993c41c6b7c65dda586a66fdd865b3afd This PR also reviews the longpress implementation and fix a Firefox glitch. task-5366875
Resolved issues and error corrections
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in multiple preparation tickets being printed. The fix ensures that preparation tickets are only generated once upon order acceptance, streamlining the process and reducing printing costs. It also removes local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103915 Forward-Port-Of: odoo/enterprise#100280
This update fixes a problem where payslips couldn't accurately reflect employee earnings from previous years. The change now allows for retroactive updates to payslip snapshots, ensuring correct calculations and reporting for historical data. This improves payroll accuracy and compliance.
Original PR description
Currently employee data only updates current year snapshots, which can be an issue when generating payslips for previous years, in this PR we enable retroactive updates by changing the mecanism. The new mecanism updates snapshots of the payslip years, making a reference date usage possible. Forward-Port-Of: odoo/enterprise#103386 Forward-Port-Of: odoo/enterprise#103147
This update fixes a visual issue where milestone deadlines weren't shown in the Project list view. The fix ensures that milestone names now include the associated deadline, providing a clearer view of project timelines. This improves project management clarity.
Original PR description
**Steps to Reproduce:** - Install the Industry FSM module. - Navigate to Project Configuration. - Enable Milestones. - Go to the Project list view. - Observe that the Next Milestone does not display the deadline along with the milestone name. **Issue:** The milestone display name is incomplete and does not include the deadline date. **Cause:** The required context was not passed in the overrided action's context, so the display_name computation did not add the deadline to the milestone name. **Fix:** Pass the appropriate context in the action to correctly compute and display the name along with its deadline. Task: 5255295 Forward-Port-Of: odoo/enterprise#103157
14 changes
Enhancements to existing features
This update adjusts the Vietnamese localization's chart of accounts to align with new accounting regulations (Circular 99/2025), effective January 2026. This change ensures compliance with current Vietnamese accounting standards and will impact financial reporting for Vietnamese businesses using Odoo Enterprise.
Original PR description
Update the COA for the vietnamese localization, which is based on the circular 200/2014 by the new one based on the circular 99/2025. This new COA applies starting in Jan. 2026 task-5357470 Forward-Port-Of: odoo/enterprise#103769 Forward-Port-Of: odoo/enterprise#102843
Resolved issues and error corrections
This update fixes a display issue in the Project Configuration module. Previously, milestone names in the Project list view were missing the associated deadline date. The fix ensures that milestone names now accurately show both the name and the deadline, improving clarity and usability for project managers.
Original PR description
**Steps to Reproduce:** - Install the Industry FSM module. - Navigate to Project Configuration. - Enable Milestones. - Go to the Project list view. - Observe that the Next Milestone does not display the deadline along with the milestone name. **Issue:** The milestone display name is incomplete and does not include the deadline date. **Cause:** The required context was not passed in the overrided action's context, so the display_name computation did not add the deadline to the milestone name. **Fix:** Pass the appropriate context in the action to correctly compute and display the name along with its deadline. Task: 5255295
This update resolves a minor issue within the sign flow process. Previously, selecting a specific dropdown item could result in an incomplete menu display. The fix ensures the menu always shows all available styles, improving the user experience and preventing potential confusion.
Original PR description
In this tour, when we want to select the third dropdown item in style list menu, we must wait that the rpc get_fonts/ is done, or else, it has only one item in the menu. When the menu is opened before the call is completed, there is only one style. When it is opened after, there is all styles loaded. runbot-error-id~232652
This update fixes a usability issue in the Sign editor where the document dropdown didn't close properly after selection. The changes include improved hover behavior, consistent styling for actions, and a fix to handle dropdown closures within the PDF iframe, ensuring a smoother user experience.
Original PR description
- Fix hover and pointer behavior on update document action - Apply consistent danger styling to delete action - Ensure dropdown closes correctly after interaction (PDF iframe has its own document so outside-click logic did not apply; add a click listener on the iframe document to close open dropdowns. ) task: 5384677
This update prevents unnecessary email reminders for timesheet approvals. The system now only sends reminders when there are actual timesheets awaiting approval, ensuring users aren't overwhelmed with notifications. This change optimizes the approval workflow and reduces email clutter.
Original PR description
prevent cron from sending approver reminder if no timesheet assigned to approver Send the reminder email if: - there are timesheets to validate - AND if the user is set as either the manager or timesheet approver of an employee with timesheets left to be validated - OR if the said employee has no manager or timesheet approver set Task-3624610 Forward-Port-Of: odoo/enterprise#102860 Forward-Port-Of: odoo/enterprise#52355
This update resolves a technical issue where the UrbanPiper POS system was incorrectly reporting an 'undefined street' error during order completion. The fix ensures that the system properly checks if a customer is assigned before finalizing an order, preventing this error and allowing customers to successfully complete their deliveries.
Original PR description
Steps to produce: ==== - Place an online delivery order through urbanpiper - Edit the order and remove customer - Complete the order as Marks as Ready - Print Reciept Issue: ==== - TB occurs stating undefined street Fix: ==== - Check whether partner is assigned or not task-5407001 Forward-Port-Of: odoo/enterprise#103633 Forward-Port-Of: odoo/enterprise#102100
This update fixes a limitation in how employee data is used for payslip generation. Now, payslips can accurately reflect past year earnings by retroactively updating snapshots, allowing for correct calculations and reporting. This ensures historical payroll data is reliable.
Original PR description
Currently employee data only updates current year snapshots, which can be an issue when generating payslips for previous years, in this PR we enable retroactive updates by changing the mecanism. The new mecanism updates snapshots of the payslip years, making a reference date usage possible. Forward-Port-Of: odoo/enterprise#103296 Forward-Port-Of: odoo/enterprise#103147
This update resolves a technical issue that caused a traceback when users accessed the bank reconciliation popover in debug mode, specifically when reconciling statements with invoices in different currencies. The fix ensures the popover component functions correctly, preventing errors and improving the user experience for this common banking task.
Original PR description
In Bank reconciliation widget, when reconciling a statement with a move in different currency, users may display a popover to access some reconciliation info. Currently, accessing this component in debug mode may raise a traceback. Steps to reproduce: - Have a Bank statement in company currency - Reconcile with an invoice in foreign currency - Go in debug mode - From the reconciliation widget, locate the reconciled bank statement - Click on the reconciled bank statement popover button Issue: Traceback is shown `OwlError: Invalid props for component 'BankRecLineInfoPopOver': 'exchangeMove' is not a object` It occurs because props validation of the Owl component will fail BankRecLineInfoPopOver opw-5355964 Forward-Port-Of: odoo/enterprise#103731
This update resolves a problem preventing connections to IAP Codaclean, which is crucial for accurate financial reporting. The issue was caused by a missing parameter in the connection process, now corrected to ensure seamless integration with Codaclean.
Original PR description
Connections to IAP Codaclean are failing because of missing `enterprise_number` param. no-task-id Forward-Port-Of: odoo/enterprise#103724
This update resolves an issue where accepting UrbanPiper online orders in multiple POS locations would trigger duplicate preparation ticket prints. The fix ensures that preparation tickets are printed only once, regardless of the number of active POS sessions, improving order accuracy and reducing unnecessary printing. This change impacts the UrbanPiper integration.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103894 Forward-Port-Of: odoo/enterprise#100280
This update fixes an issue where the 'Out of Contract' duration was incorrectly calculated, leading to inaccurate reporting. The change ensures that contract overlap dates are limited to the payslip period, providing more reliable payroll data. This improves the accuracy of employee time and cost tracking.
Original PR description
Steps to Reproduce: 1. Create a contract ending early in the year (e.g., February). 2. Compute a payslip for a much later period (e.g., November). 3. The "Out of Contract" line shows an excessive number of days (counting from Feb to Nov). Reason: - If a contract ends before the payslip period, it adds all days from the end of the contract until the end of the payslip period as "Out of Contract", ignoring the payslip start date. - If a contract starts after the payslip period, it adds all days from the payslip start date until the contract start date, ignoring the payslip end date. Solution: Constrain the calculated "Out of Contract" dates using `max()` and `min()` to ensure they never exceed the payslip's `date_from` and `date_to`. Task: 5350519 Forward-Port-Of: odoo/enterprise#103739 Forward-Port-Of: odoo/enterprise#100700
This update fixes a potential issue where the POS system incorrectly flagged refunds as exceeding order amounts due to rounding differences. The change ensures accurate comparisons between refund amounts and order totals, preventing false alerts and improving the reliability of the refund process. This resolves a technical problem related to financial reporting accuracy.
Original PR description
Before this commit, if the total amount of the order had rounding differences compared to the sum of its lines, the system could incorrectly trigger an alert stating that the refund amount exceeds the original order amount. This was due to a direct comparison between the two amounts without considering potential rounding issues. opw-5402240 Forward-Port-Of: odoo/enterprise#103551 Forward-Port-Of: odoo/enterprise#102224
Features or functions removed from Odoo
This update removes outdated configuration settings from tests related to the Co-Dian localization module. These settings were no longer needed after a previous update and were causing unnecessary complexity in the test suite. This cleanup improves test efficiency and maintainability.
Original PR description
The configuration parameter `account_edi_ubl_cii.use_new_dict_to_xml_helpers` was removed in saas-18.4. However, this parameter was still being set in various tests across `account_edi_ubl_cii`, `l10n_account_edi_ubl_cii_tests`, `l10n_hr_edi`, and `l10n_co_dian`. This commit removes these unnecessary configuration lines to clean up the tests. Related PR : https://github.com/odoo/odoo/pull/242749 Forward-Port-Of: odoo/enterprise#103766
Miscellaneous changes
This pull request updates the Odoo Enterprise repository to the 19.0 version. This ensures that users are running the latest stable release with the newest features and improvements for the Enterprise edition. It's a standard maintenance update to keep the system current.
Original PR description
Cargar repositorio 19.0 de enterprise.
1 change
New functionality added to Odoo
This update introduces a new 'test' field to partner records, allowing users to easily identify test accounts for email automation. When an email address is set to 'test@test.com', the field automatically defaults to 'testing'. Conversely, any other email address will set the field to 'none'.
Original PR description
- Add 'test' selection field (none/testing) to res.partner model - Make partner tree view editable (inline editing enabled) - Add test field to partner list view after email field - Automatically set test='testing' when email='test@test.com' - Automatically set test='none' when email changes to other value - Make user_id field required when test state is 'testing' (frontend only) 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