Friday, December 19, 2025
14 changes · 18.0
Resolved issues and error corrections
This update resolves a test failure within the Odoo Enterprise system. The issue stemmed from a configuration error related to employee accounting records, specifically concerning future holiday calculations. The fix ensures accurate record creation during testing, preventing the test from failing.
Original PR description
fixing runbot error https://runbot.odoo.com/odoo/runbot.build.error/234639 on test test_mrp_analytic_account_employee_from_widget introduced by this PR https://github.com/odoo/enterprise/pull/85517
**cause of the error:**
Because there is a resource.calendar.leave without calendar_id,
without resource_id and at a date after today :
during the setupclass, when the employee is created,
_create_future_public_holidays_timesheets() creates an account.analytic.line.
So at the end of the test ,
self.env["account.analytic.line"].search([('employee_id', '=', self.employee1.id)])
returns 2 records instead of 1.
runbot-234639
Forward-Port-Of: odoo/enterprise#102282This update resolves an issue where overdue invoices were printed twice in follow-up PDF reports. Previously, manual follow-up emails generated PDFs with the invoice listed redundantly. This change ensures invoices appear only once, improving the clarity and accuracy of these reports for users.
Original PR description
Issue: In a manual follow-up printed as PDF, overdue invoices appear twice. Step to reproduce: - Have an overdue invoice - go to the Partner > accounting, - Send manual follow-up - In the wizard select Print and "Attach Invoices" Current behavior: The PDF display the reminder, the invoice, the report and the invoice again. Expected behavior: Invoice should appear only once in the follow-up PDF. Solution: When manually sending the follow-up, the wizard attaches the invoices to the follow-up. Therefore, they were added a second time at the end of the document in `_get_followup_attachments`. opw-5368870
This update resolves an issue where users without the 'Expenses Administrator' group couldn't digitize receipts attached to expenses. The fix removes this restriction, allowing all users to digitize receipts, improving the user experience and streamlining expense reporting. This change is a minor bug fix.
Original PR description
When a regular user tries to digitize the receipt attached to an expense, the `UserError(_("You don't have the rights to bypass the validation process of this expense."))` is raised. It seems that currently, the user needs to be in the Expenses Administrator group (`group_hr_expense_manager`) to digitize the receipt, which doesn't seem correct.
The fix is proposed here: https://github.com/odoo/odoo/pull/240401. In this PR, I only added a test, which requires the PR on odoo core to be merged first.This update resolves an issue where the Shopee Buyer ID, used for integration with the Shopee marketplace, could exceed the maximum value for an integer. By changing the data type to ‘Char’, this prevents errors and ensures accurate data storage. This improves the stability and reliability of the Shopee integration.
Original PR description
Shopee Buyer ID’ retrieved from the marketplace can, in some cases, exceed the maximum value of the Integer data type. It has been updated to use the Char data type to prevent the ‘out of range for type integer’ error.
This update streamlines the HTML Editor's testing process by separating individual test calls. Previously, tests shared timeouts, leading to unreliable results. Additionally, unnecessary helper functions for tag creation have been removed, simplifying the codebase and improving clarity. This change enhances test stability and maintainability.
Original PR description
Description of the issue/feature this PR addresses: I. Grouping multiple testEditor in a single test is bad practice because the timeout of it is then shared between the different testEditor calls rather than each having their own separate timers. This PR splits the calls of each testEditor to its own test. II. This PR removes helper functions used to create different types of tags. Instead of simplifying the code, these helpers introduced unnecessary complexity and confusion. task-5375867 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update prevents the system from attempting to check the Git repository when an IoT box isn't connected to a database. This improves efficiency and reduces potential issues related to disconnected devices, ensuring smoother operation.
Original PR description
This PR ignores the call to check_git_branch if no database is connected to the iot box. Forward-Port-Of: odoo/odoo#240610
This update fixes a potential issue where printing on Windows could cause the Odoo system to fail. By adding a safety net to catch printing errors, the system is now more stable and reliable for users on Windows.
Original PR description
This commit adds the try/except block around print_raw method of the virtual iot box to allow catching exceptions when printing on Windows Forward-Port-Of: odoo/odoo#238633
This update corrects a minor issue in the Peppol registration process. Previously, the EAS field automatically received focus, which was confusing for users. This change removes the ability to focus the EAS field, ensuring the system correctly pre-selects it and streamlines the registration workflow.
Original PR description
During registration on Peppol, the eas field is focused first, which makes no sense as it's supposed to be correctly preselected, and users aren't supposed to touch it So this commit makes it non-focusable 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
A bug was preventing users from completing sign requests after a user was deleted. This fix addresses a problem where the system incorrectly handled missing user information when retrieving sign request items. By safely handling cases where user IDs are missing, the system now reliably allows users to complete sign requests without errors.
Original PR description
Currently an error occurs when a user tries to click `Valid & Send Compeleted Document` as follows below: - Install the `sign` module with demo data - Log in as the `demo` user and send 2 sign requests to the `admin` user - Now log in as the `admin` user and delete the `demo`user - Go to the sing and open sign request that was sent by the `demo` user - Complete the sign and click on `Valid & Send Compeleted Document` This issue occurred while retrieving the suggested sign request items. The code was accessing the `create_uid` of those items, but because the user had been deleted, `create_uid` was set to False instead of containing a valid user ID and user name. This commit fixes the above issue by handling cases where `item['create_uid']` is False. When `item['create_uid']` is False, the code now safely returns `False` instead of attempting to access its index. sentry-7116433081
This update corrects a technical issue in the Odoo Enterprise accounting system. Previously, a specific calculation method was always used for deferred revenue, leading to inaccurate accounting entries. This fix ensures the system correctly utilizes the deferred revenue type, improving the reliability of financial reporting.
Original PR description
In c3bd8e44546df21c51914a560a28a739f55cca21, a forward-port of 0a6bc3710ee1bfdf10bfd3da7d6e24fd190432e6, the `deferred_expense_amount_computation_method` was always used instead of relying on the deferred type opw-none
This update fixes a minor usability issue where clicking 'Jump to Present' on the desktop would cause the composer to lose focus. Now, the composer automatically regains focus after this action, streamlining the user experience and allowing for immediate typing.
Original PR description
**Current behavior before PR:** clicking "Jump to Present" caused the composer to lose focus, forcing users to manually focus the input before typing. **Desired behavior after PR is merged:** The composer automatically regains focus on desktop after clicking "Jump to Present". task-[5035977](https://www.odoo.com/odoo/project/1519/tasks/5035977) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a bug that prevented administrators from accessing employee details within the Point of Sale (PoS) frontend. The fix simply disables a feature that was causing errors, streamlining the user experience. Employee information is intended to be managed from the backend, ensuring data integrity.
Original PR description
Steps to reproduce ------------------ 1. Enable "Log in with Employees" 2. Login with any employee and make an order 3. Switch to the admin, "Mitchell Admin" usually 4. Go to the paid orders (we are still in PoS UI not in the backend), and select the order paid in step 2. 5. Click on "Details", the order form will appear, click on the "Cashier" name A traceback will appear, saying 'Cannot find key "hr_employee_form" in the "views" registry'. The fix ------- We simply disable the employee_id field; it will not try to open the employee form anymore. That is much simpler than adding all the required hr assets to the PoS frontend. Employee details are meant to be seen and navigated from the backend. opw-5252486
This update fixes a potential issue where payroll calculations could incorrectly show employees owing money to the state. The change ensures that taxable income defaults to zero when state deductions exceed gross income, preventing inaccurate payslip reporting. This improves payroll accuracy and compliance.
Original PR description
This commit simply defaults the computed taxable income amount to 0 in case the state deductions are greater than their gross income. Otherwise our payslips would imply that these employees are owed money by the state opw-5137280
Features or functions removed from Odoo
This update removes outdated code that resulted from a previous conflict resolution in the Web Studio module. This cleanup improves the stability and efficiency of the module, ensuring a smoother user experience. It's a routine maintenance task to keep our software running optimally.
Original PR description
Some old code was leftover when fixing a conflict in https://github.com/odoo/enterprise/commit/019d6bc953d214416a8807f5a26bf41a9cbe201d