Tuesday, June 30, 2026
10 changes · saas-19.3
Resolved issues and error corrections
A point-of-sale sales test was moved to the module that now contains the related stock logic. This prevents the automated build from failing and keeps the test aligned with the right feature set.
Original PR description
The test uses `pos_order.picking_ids`, but on saas-19.3 `picking_ids` moved to the `pos_stock` module. `pos_sale` does not depend on `pos_stock`, so the test fails there with AttributeError. Move it to `pos_sale_stock`, which depends on `pos_stock`. Fixing https://runbot.odoo.com/odoo/runbot.build.error/938839
This change adjusts a point of sale test so it uses a single, compatible setup instead of mixing data from different company contexts. It helps prevent test failures in multi-company environments and makes the test suite more reliable.
Original PR description
Making the test only depend on one class setup to avoid potential (already present) multicompany issues. In this case the env.user came from one setup class but was incompatible to use during the setup of the second class that was creating records for another company. By making the test only depend on one of the tests we'll avoid this issue. runbot-939375 Forward-Port-Of: odoo/odoo#268819
This change fixes a timing issue in WhatsApp channel tests where the seen status could be overwritten before the message fully loaded. As a result, the seen indicators now display reliably, reducing flaky behavior in channel conversations.
Original PR description
The "Allow SeenIndicators in WhatsApp Channels" test awaited the bus subscription so the simulated seen notification is no longer dropped, but that exposed a second race between the init RPC and the bus return. openDiscuss does not await the channel data fetch (channels_as_member), whose response carries each member seen_message_id=false. When it is applied after the _sendone seen notification, it clobbers the member back to unseen, the indicators never render, and the assertion times out. Wait for the message to render before simulating the seen notification: the thread message comes from the message fetch, which only runs once the channel (with its members) is loaded, so the seen data is guaranteed applied. This mirrors the message seen indicator tests in mail. https://runbot.odoo.com/odoo/error/242021 Forward-Port-Of: odoo/enterprise#122041
This fix makes the Point of Sale more resilient by safely handling unexpected or invalid input when checking whether an IP address is private. It avoids crashes in cases where the system receives a value that is not a string, helping keep the feature stable for users.
Original PR description
Add an extra guard to isPrivateIp to return false for invalid values. Otherwise it would throw a TB when the provided value is not a string. This fix already exists on 19.0-19.2 from [#256028](https://github.com/odoo/odoo/pull/256028) Task-[6295735](https://www.odoo.com/odoo/project/1737/tasks/6295735) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update stops users from choosing a private task as the parent of another task. It helps keep private work items properly hidden and avoids accidental exposure through task hierarchy relationships.
Original PR description
In this commit, we ensure that private tasks can never be selected as parent tasks. task-5119141 Forward-Port-Of: odoo/odoo#272263 Forward-Port-Of: odoo/odoo#270795
The Point of Sale stock tests were updated so lot tracking is set on the product template instead of the product variant. This keeps the tests working with the current Odoo behavior and helps avoid validation errors during automated testing.
Original PR description
`tracking` is no longer writable on `product.product` on 19.3/master. Update lot-related POS tests to write it on `product.template` instead. original task: 6274744 runbot error: 940485
This update corrects the alignment of the link popover’s URL field and its icon in Notes. It ensures the input keeps the same height as its container, so the interface looks consistent even when autocomplete is available.
Original PR description
Steps to Reproduce: - open notes - type `/link` to open link popover Issue: - The url input field and its icon are misaligned. Cause: - When url autocomplete are enabled in the link popover, the input field height is reduced, causing it to become smaller than its container. This results in misalignment between the input field and the icon. Solution: - Set the link popover url input height to 100% so it always matches the height of its container, ensuring proper alignment even when autocomplete is avaialble. task-6201175
This fix brings back the intended behavior for pages using the `s_nb_column_fixed` class, which hides the column count option in the builder. It ensures that layouts marked this way no longer show an option that should be locked, improving consistency for content editors.
Original PR description
The class 's_nb_column_fixed' was used to hide the column count option, but it got lost during the refactoring and doesn't work since 18.4. This commit restores it. task-6234267 Forward-Port-Of: odoo/odoo#271975 Forward-Port-Of: odoo/odoo#268005
This update makes the public chat test flow more reliable by ensuring the attachment menu closes before the message is sent. It also corrects a test setup issue so the right conversation data is updated between runs, helping prevent flaky failures during automated testing.
Original PR description
Attempt at fixing the following race condition. It's not clear what causes it, but these changes make the test more robust and might help future investigations. discuss_channel_public_tour opens the composer "More Actions" menu to attach files but feeds the hidden file input directly, so the menu is never closed and is still open when Send is clicked. Close it and wait for it to disappear before sending, to avoid clicking Send while the dropdown is dismissing. Also fix _open_group_page_as_user, which updated the last message body of self.channel instead of self.group between the two tour runs. https://runbot.odoo.com/odoo/error/243436 Forward-Port-Of: odoo/odoo#272606 Forward-Port-Of: odoo/odoo#272425
This change prevents Romanian-specific stock batch behavior from being applied in situations where it should not be. It fixes an error that affected automated system checks and helps keep the stock workflow stable.
Original PR description
The Romanian specifics were applied without condition which caused runbot errors. Note that this was revealed later on (saas-19.3) after a change in the generic stock test setup. runbot-241098 Forward-Port-Of: odoo/odoo#271985