Odoo Changelog — 2026-03-15

Sunday, March 15, 2026

2 changes · saas-19.1

Bug Fixes(2)

Resolved issues and error corrections

[FIX] hr_livechat: update My Team filter in Live Chat reports

Coresaas-19.1hr_livechat

This update enhances the ‘My Team’ filter in Odoo’s Live Chat reports. It now accurately reflects the team structure by including not just the user's direct reports, but also those managed by the user. This provides a more complete and useful view of team activity within Live Chat.

Original PR description

Replace the department-based domain with a hierarchy-based domain in livechat reports. The new filter includes the current user's records and the records of employees whose manager is the current user.

task-6030147


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#253567

#reporting#livechat#team

[FIX] delivery_stock_picking_batch: auto batch pickings with carrier set after confirmation to correct batch

PR #254042

Coresaas-19.1delivery_stock_picking_batchstock_deliveryMEDIUM

This update fixes an issue where automatic batch pickings didn't correctly group deliveries with carrier changes after order confirmation. Now, when you change the carrier during the delivery process, the new batch will be associated with the originally selected carrier, ensuring accurate batch management. This improves order fulfillment efficiency.

Original PR description

**Problem:**
If you have group by carrier option in automatic batches, when you create an SO with a stocked product, confirm the order, and in the delivery step you set/change a carrier, it creates a new batch transfer, and it doesn't group it with the appropriate batch with that carrier.

**Steps to reproduce:**
1) In the settings enable: Batch, Wave & Cluster transfers
2) Inventory > Configuration > Warehouse Management > Operation types
3) Enable Auto-batches, Batch grouping by carrier on Delivery orders
4) Make sure there is no batches made before contains the carrier you're going to use (to cleanly test this issue)
5) Make a sales order, add storable product, press on 'Add shipping' button and add 'standard delivery'
6) Go to the delivery of the pick from the smart button > validate it
7) Go to the next transfer to see the batch number
8) Make a new sales order, add storable product > confirm it > go to the delivery step > additional info
9) Add 'standard delivery' in the carrier field > validate the delivery > go to the next transfer button
10) check the batch it got added to, you will find it is a new one and didn't get grouped to the last batch created with the same carrier.

**Expected behaviour:**
It should get grouped in the batch containing that same carrier.

**Cause:**
When the SO is confirmed without a carrier, and then you edit the carrier in the delivery step (pick) then press on validate, it gets the carrier from the vals in the SO (blank), then along the way while validating the pick, `find_auto_batch` gets called with the empty carrier, so it creates a new batch, *AND then* it propagates the carrier from the SO to the pick using `get_new_picking_values` method, but by then it's too late as the batch is already created with the blank carrier.


**Solution:**
The problem happened because of this commit: https://github.com/odoo/odoo/commit/7c32adcd82119c35485addd1b198a7fcc0053c9f
We need to add the propagation of the carrier_id to the vals if it was already changed or set before the validation of the pick.

opw-5882310

Forward-Port-Of: odoo/odoo#248490

#delivery#batch#carrier#order fulfillment

Replace the department-based domain with a hierarchy-based domain in livechat reports. The new filter includes the current user's records and the records of employees whose manager is the current user. task-6030147 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#253567

**Problem:** If you have group by carrier option in automatic batches, when you create an SO with a stocked product, confirm the order, and in the delivery step you set/change a carrier, it creates a new batch transfer, and it doesn't group it with the appropriate batch with that carrier. **Steps to reproduce:** 1) In the settings enable: Batch, Wave & Cluster transfers 2) Inventory > Configuration > Warehouse Management > Operation types 3) Enable Auto-batches, Batch grouping by carrier on Delivery orders 4) Make sure there is no batches made before contains the carrier you're going to use (to cleanly test this issue) 5) Make a sales order, add storable product, press on 'Add shipping' button and add 'standard delivery' 6) Go to the delivery of the pick from the smart button > validate it 7) Go to the next transfer to see the batch number 8) Make a new sales order, add storable product > confirm it > go to the delivery step > additional info 9) Add 'standard delivery' in the carrier field > validate the delivery > go to the next transfer button 10) check the batch it got added to, you will find it is a new one and didn't get grouped to the last batch created with the same carrier. **Expected behaviour:** It should get grouped in the batch containing that same carrier. **Cause:** When the SO is confirmed without a carrier, and then you edit the carrier in the delivery step (pick) then press on validate, it gets the carrier from the vals in the SO (blank), then along the way while validating the pick, `find_auto_batch` gets called with the empty carrier, so it creates a new batch, *AND then* it propagates the carrier from the SO to the pick using `get_new_picking_values` method, but by then it's too late as the batch is already created with the blank carrier. **Solution:** The problem happened because of this commit: https://github.com/odoo/odoo/commit/7c32adcd82119c35485addd1b198a7fcc0053c9f We need to add the propagation of the carrier_id to the vals if it was already changed or set before the validation of the pick. opw-5882310 Forward-Port-Of: odoo/odoo#248490