Tuesday, July 14, 2026
33 changes · saas-19.3
New functionality added to Odoo
This pull request updates the Odoo localization files to include translations for the PayU payment method. This addition allows Odoo users to accept payments through PayU, expanding payment options and supporting international business operations. The change is part of a broader effort to improve localization and support new payment gateways.
Original PR description
Forward-Port-Of: odoo/odoo#275865
Enhancements to existing features
Signature requests created from other apps now include the document template name alongside the related record name. This makes request names, file names, and email subjects easier to recognize and less likely to be confused with the signer’s name.
Original PR description
When requesting a signature from another app, the request name, filename and email subject only showed the linked record name, which often read as the signer's name. The template name is now added so all three follow the same "<prefix> - <template> - <record>" format. task-6317174 Forward-Port-Of: odoo/enterprise#122963
Resolved issues and error corrections
Printing an appraisal form from the action menu now waits briefly so the menu can close first. This prevents the menu from appearing on printed appraisal documents, giving users cleaner and more professional printouts.
Original PR description
When printing the appraisal form from the action (cog) menu, the drop down menu itself was incorrectly showing up in the printed document. This happened because the browser started printing immediately before the menu had time to close. By adding a small delay before triggering the print action, the menu now has time to completely close, so it no longer appears in the final print. task-6369240 Forward-Port-Of: odoo/enterprise#123242
Features or functions removed from Odoo
This update simplifies the restaurant POS system by standardizing payment method naming conventions. The team has replaced older, snake_case methods with camelCase equivalents, improving code consistency and maintainability. This change ensures smoother integration and future development of the restaurant POS module.
Original PR description
In this commit: - Use the new method names in the payment adjustment flow. - Replace deprecated snake_case methods with their camelCase equivalents for payment lines, payment terminals, and order totals. Task:6049128 Forward-Port-Of: odoo/odoo#271792
The Sendcloud delivery settings now use the term "Use Multicollo" instead of "Use Batch Shipping." This aligns Odoo wording with Sendcloud terminology, reducing confusion for users configuring shipments.
Original PR description
In order to avoid confusion for the customer, "Use Batch Shipping" was renamed to "Use Multicollo".This way it is consistent with the terminology used by Sendcloud. task-6048477 Forward-Port-Of: odoo/enterprise#122920 Forward-Port-Of: odoo/enterprise#122133
This update adds the Belgian CODA extension number entry to the translation configuration. It helps ensure this accounting-related term can be managed consistently in translations, with no expected change to day-to-day workflows.
Original PR description
This commit will add l10n_be_coda_extension_number in the weblate json file. no task id Forward-Port-Of: odoo/enterprise#124053
This update makes the database authentication module available for translation, helping users work with clearer wording in supported languages. It also corrects minor text mistakes and tidies an internal validation case that users would not normally encounter.
Original PR description
The aim of this commit is to allow the translator to work on this module translation and fix a typo that was made. Task-id: None Forward-Port-Of: odoo/enterprise#124038
AI tool failures caused by invalid model inputs are now logged without full error tracebacks, reducing noisy system logs. Detailed traceback information remains available in debug logs for troubleshooting when needed.
Original PR description
Tool failures from bad LLM arguments were logged at ERROR level with a full traceback, polluting the logs. I have changed the logger to log error not exception so we get rid of the traceback error added another debug logger to show the traceback also task-6250418
Sendcloud shipping labels now correctly keep dots in street numbers, such as “12.345,” instead of shortening them to “12.” This helps prevent incorrect delivery label data for customers whose addresses use dotted house numbers.
Original PR description
Issue ----- Labels have unexpected format when the delivery address has a dot (`.`) in the number. Steps to reproduce ----- - Set up Sendcloud (carrier shouldn't matter) - Enable logs - Create a customer (with valid address, phone and email) - Address must contain a dot, eg Grand Place 12.345 - Deliver a product to the customer - Add sendcloud as delivery method - Go to the logs - Open the "sendcloud request parcels" log > house_number is 12 Cause ----- The `house_number` field is populated using `_get_house_number`, where the regex used to extract the number from the address line does not accept the `.` character. https://github.com/odoo/enterprise/blob/f93882555864a1f0a2a3e3863780096c78923bfa/delivery_sendcloud/models/sendcloud_service.py#L323 ----- Ticket: opw-6295904 Forward-Port-Of: odoo/enterprise#123820 Forward-Port-Of: odoo/enterprise#123266
AI conversations now wait until loading is complete before showing the initial start message. This prevents users from seeing a brief empty chat screen and makes AI chats feel consistent with regular Discuss conversations.
Original PR description
Only display the AI thread start message once the thread has finished loading, matching the behavior of regular Discuss channels and preventing a brief flash of the empty conversation. Update the AI-specific `showStartMessage` implementation to respect the base Thread loading state instead of always displaying the start message for AI channels. Community PR : https://github.com/odoo/odoo/pull/273991 task-6352578
This fix prevents an error when the Timesheet app processes away-status activity without an expected unmatched group. It helps keep the timesheet grid stable and avoids interruptions for users reviewing or entering time.
Original PR description
Before this commit, when the unmatched group is not found in events before processing afk event, a traceback occurs saying `Cannot read properties of undefined (reading 'Away (afk status 1)')` This commit moves the code checking the group key exists in `this.state.grouped` after processing afk event and before adding the afk event in unmatched group. Forward-Port-Of: odoo/enterprise#123452
Previously skipped checks for rental stock valuation and Kenyan electronic stock reporting have been restored and updated after recent valuation changes. This helps ensure stock receipts are valued consistently from vendor bills, reducing the risk of accounting or reporting regressions.
Original PR description
*: sale_stock_renting, l10n_ke_edi_oscu_stock Re-enable and adapt the tests skipped to fast merge the valuation refactoring made in 08b62a4bbcc6f9a391b2cc00a621ef4c76100229. The stock IO now values the receipt from the vendor bill, so the shared purchase fixtures `l10n_ke_edi_oscu` need to match the values provided in `l10n_ke_edi_oscu_stock` see for instance: https://github.com/odoo/enterprise/blob/ce68644f97ac28568b9497a18079a4ad5ce4a125/l10n_ke_edi_oscu/tests/expected_requests/save_purchase_2.json#L11-L13 Forward-Port-Of: odoo/enterprise#122857
Obox modules are now included in the translation setup, so their text can be translated for users in different languages. This fixes an earlier setup gap and helps provide a more consistent localized experience.
Original PR description
When the Obox modules were added in odoo/enterprise#110834 they were not also added to `.weblate.json`, meaning they will not be translated. This commit fixes the issue. Forward-Port-Of: odoo/enterprise#124025
Point of Sale receipts will no longer include the extra terminal receipt generated by Worldline payments. This keeps customer receipts cleaner and avoids duplicate or unnecessary payment details being printed.
Original PR description
This PR removes the terminal receipt from Worldline we are currently inserting in the Point Of Sale receipt We don't adapt the driver code to get the receipt as we cannot change C method prototypes task-6373975 Forward-Port-Of: odoo/enterprise#123770
This update removes a reference to a non-existent user group from Belgian payroll fleet fields. It prevents configuration issues caused by linking fields to an invalid group, with no expected change to normal payroll or fleet workflows.
Original PR description
The group hr_group_user does not exist and shouldn't be linked to these fields. task-6369268 Forward-Port-Of: odoo/enterprise#123238
Salary simulations for Belgian payroll now ignore earlier payslips from the same month when calculating items such as the employment bonus. This prevents past payroll data from skewing simulated results, giving HR teams a clearer estimate before final processing.
Original PR description
Some computations such as the employment bonus rely on the previous payslips of the month. In case of salary simulation, we shouldn't take these into account to have an accurate result. task-6385091
Clearing the start or end date on a field service planning shift no longer causes an error when break time is recalculated. This makes schedule editing more reliable for users managing field service shifts.
Original PR description
before: when removing the start and end date of a shift, a trace back happens in the `_onchange_break_time` cause: it depends on the start and end date values, so it breaks when they are falsy after: apply a guard to the `_onchange_break_time` function to check on those fields to avoid breaking it --- task-6361418 Forward-Port-Of: odoo/enterprise#123273
This fixes an issue where product item update requests in the pricing tool were sent with inconsistent data after a recent update. It helps ensure price-related product information is synchronized reliably without changing the user workflow.
Original PR description
odoo/enterprise#120226 FW port introduced an inconsistency in the data passed to the items update request. This commit fixes it.
This update fixes an issue where down payment invoices generated from POS wouldn't correctly display the original line name. Previously, the system incorrectly used the sale order line's name instead. Now, down payment invoices maintain their own unique line names, ensuring accurate invoice reporting and customer clarity. This resolves a previous bug impacting POS transaction accuracy.
Original PR description
When a POS line comes from a sale order, its invoice line name is overridden with the source sale order line's name. When a down payment is invoiced directly from the POS, the invoice is generated before the down payment POS line is linked to its sale order line, so sale_order_line_id is still empty and the override resolved to an empty recordset, setting the invoice line name to False. Only override the name when a sale order line is actually set, so the down payment line keeps its own name. opw-6305649 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#274000
This update resolves a technical error that occurred when users opened the Gmail add-in after sending an email to themselves within Odoo. The fix ensures that self-sent emails can now be reliably accessed and opened through the Gmail integration, improving usability for internal communications.
Original PR description
Bug === If we email ourselves, and open the Gmail addin on it, then an error is raised. Task-6375862 Forward-Port-Of: odoo/odoo#275810
This update fixes a bug that occurred when navigating the order tour on slower browsers. Specifically, jumping to a pinned message caused a scroll race, leading to timeouts and the tour failing to complete. The fix ensures the tour waits for the pinned message to fully scroll before proceeding, improving navigation reliability.
Original PR description
Jumping to the pinned message highlights it and asynchronously scrolls it into view. On a slow browser that scroll can land right after the tour scrolls to the bottom and pull the thread back up to the pinned message. The load-newer observer callback, which awaits the highlight scroll before re-checking visibility, then finds the bottom sentinel hidden and drops the fetch of the following messages, so the final :count(60) step never matches and times out. Wait for the pinned message to be scrolled into view and for its highlight to clear (its scroll is then finished) before scrolling to the bottom, so the jump scroll no longer competes. https://runbot.odoo.com/odoo/error/941509 Forward-Port-Of: odoo/odoo#275289
This update resolves a hidden error in the mass mailing module that was causing loading problems, even when the component was already finished. The fix ensures smoother operation and prevents potential disruptions to email campaigns.
Original PR description
Commit [1] introduced an erroneous `!` operator before status, that would throw loading errors even if the component was already destroyed (those errors should be masked). [1]: https://github.com/odoo/odoo/commit/51c7846f99eb061a1d71ca5d9967f5b01f5551a1 Forward-Port-Of: odoo/odoo#275785
This update resolves an issue where triple-clicking within inline editable content caused the selection to extend beyond the intended area. The fix ensures that triple-clicks accurately select the inline content, improving the user experience within the HTML editor.
Original PR description
Problem: Triple-clicking inside an inline `contenteditable="true"` element causes the selection to extend outside of it. Cause: Inline `contenteditable="true"` elements are not considered when looking for the closest block boundary, allowing the browser selection to expand beyond the editable content. Solution: Treat `contenteditable="true"` elements as block boundaries when searching for the closest block. Steps to reproduce: - Add an inline `contenteditable="true"` element inside an editable area. - Triple-click inside it. - Observe that content outside the `contenteditable` element is also selected. task-6255094 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#267487
This update ensures that the Pos Cashmatic module's text is properly translated into other languages. By adding the module to the translation files, the system will now display the correct text for users in different regions. This improves the user experience and expands the module's accessibility.
Original PR description
This commit add the pos_cashmatic module inside the .weblate.json file so that the srings are translated. 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 Forward-Port-Of: odoo/odoo#275863
This update fixes a visual issue in the API keys kanban view where scope and expiration information for scoped keys were displayed together as one line. The change now presents these details as separate blocks, improving readability and clarity for users managing API keys. This ensures all key information is easily accessible.
Original PR description
The API keys kanban rendered the "Scope:" and "Expires on:" hints as two adjacent inline <small> elements. For a scoped key both are visible, so they were displayed stuck together, e.g. "Scope: rpcExpires on: ...". Render each hint as a block so they stack on their own lines. Keys without a scope are unaffected since the scope hint stays hidden. Description of the issue/feature this PR addresses: Current behavior before PR: <img width="980" height="414" alt="image" src="https://github.com/user-attachments/assets/6cd8b338-1d2e-4abb-a90b-03218aaef941" /> Desired behavior after PR is merged: <img width="979" height="389" alt="image" src="https://github.com/user-attachments/assets/83ffa680-ffb8-415f-af3f-8e53cb8e8351" /> --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#275869
This update fixes a visual glitch where an empty AI conversation thread would briefly flash on the screen. The change ensures the AI thread start message only appears after the thread has fully loaded, aligning with the standard display of regular discussion channels. This improves the user experience and prevents a distracting visual issue.
Original PR description
Only display the AI thread start message once the thread has finished loading, matching the behavior of regular Discuss channels and preventing a brief flash of the empty conversation. Update the AI-specific `showStartMessage` implementation to respect the base Thread loading state instead of always displaying the start message for AI channels. Enterprise PR : https://github.com/odoo/enterprise/pull/122808 task-6352578 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update streamlines the process of logging out employees in the Point of Sale system. By reducing the idle timeout, the system now automatically logs out staff more quickly, improving efficiency and security. This change was implemented as a bug fix to address a reported delay in employee logout.
Original PR description
Reduce idletimeout task id: 6374370 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#275081
This update corrects a bug where an attendance record was incorrectly created when an employee took time off. The fix ensures that attendances are only generated when absences are justified, preventing misleading log notes and inaccurate attendance data. This change was introduced in a previous version and has been resolved.
Original PR description
# How to reproduce - In the settings, enable Absence Mangement - Create an employee with a Contract - Create a Time off for that employee for yesterday - Manually run the scheduled action…
# How to reproduce - In the settings, enable Absence Mangement - Create an employee with a Contract - Create a Time off for that employee for yesterday - Manually run the scheduled action "Attendance: Detect Absences for employees" - Go to the attendance dashboard for that employee # The issue An attendance with no overtime was created for yesterday for that employee with a log note saying "This attendance was automatically created to cover an unjustified absence on that day." However, the absence was justified as the employee took a time off. # Cause of the issue When running the `_cron_absence_detection` cron job, we create "empty" attendances for the employees that were absent yesterday. If those attendance's `overtime_hours` are 0, then we unlink them : https://github.com/odoo/odoo/blob/a73428187112b3948a11810abae2a3c82c9c7bcd/addons/hr_attendance/models/hr_attendance.py#L659-L666 But, since `check_in` and `check_out` cannot be the same, we cannot really create an empty attedance. We instead create an attendance of 1 second : https://github.com/odoo/odoo/blob/a73428187112b3948a11810abae2a3c82c9c7bcd/addons/hr_attendance/models/hr_attendance.py#L652-L653 This will create an overtime of 0.003 seconds if there was a leave that day (which is our case). This duration will be reflected in the attendance's `overtime_hours`. The issue is that we simply do `== 0` when trying to find the attendances without overtime, so we don't unlink them. The issue was introduced by : https://github.com/odoo/odoo/commit/8d7859a569d9ac7303ca0b9be6c56496be14c544 Because `round(0.003, 3)` => 0 but `round(0.003, 4)` => 0.003 The issue is not present in 18.0+ because we don't create overtime if the duration is `float_is_zero(overtime_duration, 2)` : https://github.com/odoo/odoo/blob/39cce855aa27aa4af9225a61a3e1425383a9f49f/addons/hr_attendance/models/hr_attendance.py#L405 opw-6321883 Forward-Port-Of: odoo/odoo#275133 Forward-Port-Of: odoo/odoo#272089
This update resolves an issue where invoices were incorrectly displaying a small additional charge (0.01$) due to a misinterpretation of loyalty programs as refunds. The fix ensures that loyalty programs are properly accounted for during tax calculations, resulting in accurate tax amounts on invoices. This improves the reliability of the POS order process.
Original PR description
When computing taxes for the order, we group the base lines based on a grouping key. One of the components of this key is `is_refund`, and reward lines where considered as refund lines, which caused…
When computing taxes for the order, we group the base lines based on a grouping key. One of the components of this key is `is_refund`, and reward lines where considered as refund lines, which caused them to be grouped separately. This caused a discrepency between the tax amount computed in the frontend and the one computed in the backend. Steps to reproduce: ------------------- * Change the rounding method to globally * Create a 21% tax not included in price * Create a product with a price of 76.01 and the tax created above * Create a loyalty program with a 10% discount * Create a POS order with the product above and apply the loyalty program * Validate the order and generate the invoice > Observation: The invoice states that 0.01$ is still due Why the fix: ------------ In `round_tax_details_tax_amounts`, we try to detect any delta with the expeced tax amount. To do that we group the base lines based on a grouping key. The grouping key `is_refund` was incorrectly set to `true` for reward lines, which caused them to not be grouped. The delta was then not detected and tax amounts were not adjusted. We now make sure not to consider reward lines as refund. opw-6052112 Forward-Port-Of: odoo/odoo#275350 Forward-Port-Of: odoo/odoo#271577
This update resolves a bug where the company logo option in the website navigation wasn't correctly hiding when switching between image and text logo formats. The fix ensures the logo toggle works as expected, providing a consistent brand experience for users. It was necessary to update how the system reads configuration settings for the website logo.
Original PR description
Steps to reproduce: - Enter in edit mode - Click on the navbar logo - Change "Logo" option from "Image" to "Text" - Toggle "Company Logo" in "Visuals" option - Traceback appears: it should hide the logo This commit awaits `loadConfigKey` so `websiteLogoParams` reads the loaded config; otherwise the button targeted the wrong brand view and collided on the `#o_fake_navbar_brand` xpath. task-6284593 Forward-Port-Of: odoo/odoo#275363
This update fixes an issue where discount lines in the TBAI XML file generated for electronic invoicing were incorrectly showing negative import values. The fix ensures that all monetary values, including discounts, are consistently represented as positive numbers, aligning with previous assumptions and improving data accuracy for tax reporting.
Original PR description
Step to reproduce: - install pos_discount and l10n_es_edi_tbai_pos with demo data - start pos, add a product and a discount of 10% - fulfill the order - go to backend and open that order - from…
Step to reproduce: - install pos_discount and l10n_es_edi_tbai_pos with demo data - start pos, add a product and a discount of 10% - fulfill the order - go to backend and open that order - from "TicketBai" page, open the "TicketBAI Post File" xml file Observation: - `ImporteUnitario` and `ImporteTotal` were exported as positive values for discount lines. cause: - Commit [1] assumed tax details are always positive. - This is not generally true, in case we have price_unit < 0 - The logic relied on `is_refund`, which depends on `qty * price`. - `_l10n_es_tbai_get_values` then multiplied values by `-1` again for refunds. https://github.com/odoo/odoo/blob/e751fa1e010dbda63903d598048ef415709b4af4/addons/l10n_es_edi_tbai_pos/models/pos_order.py#L177-L181 - For discount lines, `is_refund = True` and `price = -10`, resulting in `-10 * -1 = 10`. Fix: - Ensure tax detail values are always returned as positive values, matching the assumption introduced in commit [1] [1] https://github.com/odoo/odoo/commit/03d55104e49aa65aa4c6475e199747fe9132e754 opw-6226003 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#275451 Forward-Port-Of: odoo/odoo#265777
This update resolves a problem where employee working schedules weren't consistently synchronized with their associated resource records, particularly after creating future versions. This prevented incorrect scheduling data from appearing in the Attendance Gantt view, ensuring accurate employee availability. The fix ensures schedules are always up-to-date.
Original PR description
Steps to reproduce: 1. Create a new version on an employee with a future start date 2. Ensure the new version has a different working schedule 3. After the new version becomes active, observe that…
Steps to reproduce: 1. Create a new version on an employee with a future start date 2. Ensure the new version has a different working schedule 3. After the new version becomes active, observe that the working schedule on the employees record is different from the one on the employee's resource record Every employee has an associated resource record associated with them. Normally, the employee's working schedule (`hr_employee.resource_calendar_id`) should always be in sync with their associated resource record (`hr_employee.resource_id.calendar_id`). When we update the employee's working schedule through the UI on a currently active version, it will also update their associated resource record with the same working schedule. However, if we change the working schedule for a future version, when `_cron_update_current_version_id()` runs and changes the active version, there is no mechanism to update the associated resource with the new working schedule. This change will ensure we keep the working schedules in sync, as if they are not, strange behaviors can occur. One side effect of this problem: When a new version becomes active, and working schedules become de-synced, this can cause the Attendance gannt view to display incorrect unavailable intervals for an employee (this appears as a grayed-out time slot). This is because `_attendance_intervals_batch()` pulls from the working schedule of an employee's associated resource record, rather than the employee record itself. This is what occurred on the linked ticket. [opw-6352770](https://www.odoo.com/odoo/my-tasks/6352770?debug=assets) Forward-Port-Of: odoo/odoo#275430
This update resolves an issue where Chrome was incorrectly suggesting previous selections in empty 'SelectMenu' fields. This prevented users from starting fresh with each new record creation, leading to a confusing user experience. The fix disables browser autocomplete for these fields, ensuring a cleaner and more intuitive selection process.
Original PR description
Chrome keeps suggesting autocompletion on empty selection field. https://github.com/odoo/odoo/commit/5e7bc4ab851dba3d2e0b965f69e06cfeacec5674 is the commit introducing `autocomplete="selectMenuAutocompleteOff"` and I don't know why this value has been chosen but Chrome seem to consider this token as invalid Steps to reproduce: - Put a selection field on a form view with Studio - Create a record, complete the selection field and save - Create a new record and click on the selection field Current Behaviour: Chrome keeps suggesting the previously filled values Desired Behaviour: No autocomplete from the browser. Forward-Port-Of: odoo/odoo#274527 Forward-Port-Of: odoo/odoo#274086