Monday, April 6, 2026
3 changes · saas-19.2
Enhancements to existing features
This update quietly displays a notification within WhatsApp channels when a new template is sent. This prevents distracting pop-ups, particularly when multiple templates are used, ensuring a smoother experience for users and reducing potential interruptions in conversations.
Original PR description
When a different user sends a WhatsApp template, a warning notification is posted in the active channel indicating that future replies will be moved to a new chat. This notification is now posted silently to avoid unnecessary popups, especially when templates are sent in bulk to multiple contacts with ongoing conversations. Forward-Port-Of: odoo/enterprise#112961
Resolved issues and error corrections
This update resolves an issue where tracker numbers weren't being displayed correctly in the order details after completing a self-order kiosk transaction. The fix ensures that the tracker number is accurately recorded and visible when reviewing the order in the backend. This improves the clarity and accuracy of order tracking for staff.
Original PR description
Step to reproduce: - install "pos_self_order" - have a kiosk type pos, with "service at" = "table" - start kiosk and fulfill a order - on confirmation page, add a tracker number for that order. - go to backend and open that order Observation: - check "order name" in "Extra info" page, we do not get tracker number Cause: - After this commit [1], the tracker data is overridden by next if blocks - hence the data is lost. Fix: - fix the condition. [1] https://github.com/odoo/odoo/commit/c3ea329f1dce44c668e4907fa98cb5104ed11741 opw-5975717 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#253304
This update corrects an issue where new lines added to purchase orders were causing a system error. The problem stemmed from a minor coding oversight during a recent update, preventing the correct setting of the 'date_promised' field. This fix ensures that purchase order lines are properly created and processed, improving order management.
Original PR description
How to reproduce: - Install both Purchase and Inventory application - Create a PO with Vendor X (with a purchase line to be able to create a picking but the purchase line in itself will not matter) -…
How to reproduce: - Install both Purchase and Inventory application - Create a PO with Vendor X (with a purchase line to be able to create a picking but the purchase line in itself will not matter) - Confirm Order > Receive - Add a new move line with any product and atleast one quantity - Validate - Try to access or create any PO with the Vendor X The problem: A traceback is shown Cause: When accessing or creating a new PO with Vendor X, we compute his `on_time_rate`. During this computation, we filter the moves using their purchase line's `date_promised` https://github.com/odoo/odoo/blob/7e60b3f3da2d7991220b164046a179b224384f9e/addons/purchase_stock/models/res_partner.py#L57 Commit [1] altered the behavior when creating new lines in a picking and a slight oversight was made while forward-porting : https://github.com/odoo/odoo/blob/7e60b3f3da2d7991220b164046a179b224384f9e/addons/purchase_stock/models/purchase_order_line.py#L102-L105 This makes it so `date_promised` is not set for these new lines and stays `False`. Calling `.date()` on a bool creates a traceback That said, the compute method should also be more robust since the field `date_promised` is not required. opw-6082456 [1] https://github.com/odoo/odoo/commit/52da6f77f7bf053b448f602196175b1354f70702 Forward-Port-Of: odoo/odoo#257341