Thursday, April 24, 2025
4 changes · saas-18.1
Resolved issues and error corrections
The Point of Sale debug tools now support importing paid orders, matching the existing export option. This completes the export/import workflow for support teams who need to investigate issues or move order data during troubleshooting.
Original PR description
Before this commit, it was possible to export paid orders from the debug window, but importing them was not possible. This commit allows importing orders, making the export/import flow complete and usable for debugging or data transfer purposes. opw-4688082 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Refreshing the Point of Sale screen no longer changes the order of product categories. Categories now keep the intended business-defined sequence, making navigation more predictable for cashiers.
Original PR description
Prior to this commit, refreshing the PoS caused the category order to default to ID-based sorting from IndexedDB. This commit fixes the issue by sorting categories based on their sequence. opw-4725408 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a timing issue in automated mail tests that could incorrectly fail when checking edited message labels. It helps keep validation stable without changing the user-facing mail experience.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/204922 PR above improved visual of (edited) label so that this is inline to the message content. Due to implementation details, it adds new test coverage when saving an edited message without changes, which may not have (edited) label with a simpler fix and this would be obviously a bug. The new steps to test may do `ctrl-ENTER` too soon, which would lead to not saving the message edition and instead the message is still being edited. As a result, this assertion would fail: ``` Failed to find 1 of ".o-mail-Message-content" with text "edited again (edited)" (Timeout of 3 seconds). Found 0 instead. ``` This commit fixes the issue by awaiting that the message being edited shows the input with message content in textarea, ensuring the user can actually edit the message and thus the ctrl-ENTER shortcut works and saves the message edition. runbot-1629170
Payroll users can now add a dated history line to salary rule parameters without triggering an error. This keeps payroll configuration workflows smooth when creating new rule parameter entries with initially empty values.
Original PR description
The error occurs when attempting to add a date in line in the Salary Rule Parameters Steps to Reproduce: --- - Install the `hr_payroll` module - Payroll > Configuration > Rule Parameters - Create New > History > Add a Line > Add Date Traceback: --- AttributeError: 'bool' object has no attribute 'replace' At [1], this error occurs because `value_id.parameter_value` is False. This happens because first we're adding a date, so `value_id.parameter_value` is initially empty. [1]- https://github.com/odoo/enterprise/blob/b52a93da7d680b60646cb08a9126cf6c12f5307d/hr_payroll/models/hr_rule_parameter.py#L101-L102 sentry-6531613276