Daily updates from Odoo
Wednesday, March 8, 2023
3 changes
Resolved issues and error corrections
A small issue in the Website Knowledge feature was corrected after an earlier internal update changed how field information is passed. This helps ensure copy-to-clipboard fields keep working reliably for users.
Original PR description
This commit fixes a bug introduced by a change in the standardFieldProps changed in [this commit](https://github.com/odoo/odoo/commit/688986f888f2fe2371d58b74ded81315ba6bb353#diff-1aae968392d4816e198af17d114c02b971d75d3634e8330d026fd6c9741feb38) We need to remove the key *value* from the props of the CopyClipboardCharField component, the Component in the template was forgotten when transitioning to the new standardFieldProps. task-3223259
Field Service task search screens now include the same property fields already available in Project task searches. This fixes an inconsistency and helps teams find and filter Field Service tasks using the expected custom property information.
Original PR description
Property fields introduced in the task search views in https://github.com/odoo/odoo/pull/101901 were only appearing in the Project tasks search views. This PR adds them to the Field Service search views too. Community: https://github.com/odoo/odoo/pull/114647
This fixes an unstable automated test for Mexican point-of-sale invoicing by ensuring it selects a paid order only after paid orders are actually loaded. The change reduces false test failures and helps keep delivery checks reliable without changing user-facing behavior.
Original PR description
In the tour `tour_invoice_previous_order`, we create, validate and pay an order. Then, we go to the menu presenting the existing orders. In this menu, we can filter the orders to get only the paid ones. Clicking on one of these filters triggers a fetch to the server and the records are sometimes loaded with a tiny delay.
This delay is causing an indeterminism: since the next step is to select the first order in menu (`div.order-row:first`), we sometimes select the current empty order, because the paid orders have not been loaded yet. Adapting the trigger to select only the first *paid* order solves the issue (`div.order-row:contains('Paid'):first`).
See for instance: https://runbot.odoo.com/runbot/build/24777641