Odoo Release Updates
Every commit to Odoo Community and Enterprise, parsed and categorized. Never miss a bug fix, improvement, or new feature.
Activity
2026-04-10
[IMP] mrp, purchase, sale: reorder `In the order` filter in product catalog
2026-04-07
[FIX] mrp{,_subcontracting}: group resupply pickings after PO confirm
[FIX] *: forms: boxed title and adjusted font size
2026-04-03
[FIX] stock: incorrect sequence if adding a product manually in picking
2026-04-02
[IMP] product: allow defining specific UoMs/packagings per variant
2026-04-01
[FIX] mrp, purchase_stock: assign warehouse in sudo
2026-03-31
2026-03-28
[PERF] purchase_mrp: cache cost share scan during bom explode
[FIX] purchase_stock,mrp: prevent buy to resupply from reenabling automatically
2026-03-23
This fix prevents Manufacturing Orders (MOs) from sharing purchase order references when duplicated. Previously, when an MO was copied, its reference_ids field was also duplicated, causing the new MO to become incorrectly linked to the original MO's purchase order. This resulted in quantities being consolidated on a single PO instead of creating separate purchase orders for each MO. The fix adds copy=False to the reference_ids field definition to ensure each duplicated MO gets its own independent reference records.
[FIX] mrp: prevent duplicated MO from reusing same reference
This commit refactors Odoo's field tracking infrastructure to simplify the API and improve code organization. It introduces a new mail.track.mixin that separates tracking value generation from message posting, adds new _track_add and _track_record methods to replace manual tracking value manipulation, and renames _track_subtype to _track_log_get_default_subtype for clarity. The changes eliminate low-level data structure handling across multiple modules (account, CRM, HR, fleet, Peppol) while adding comprehensive test coverage for various tracking scenarios including parent model logging and manual tracking calls.
[IMP] mail: cleanup and test tracking usage
This commit applies a systematic OWL3 migration across the entire Odoo codebase by prefixing all template variable references with "this." to comply with upcoming OWL3 requirements. In OWL3, component instance properties must be explicitly accessed via "this." in templates, changing from implicit scope resolution to explicit context binding. This large-scale automated refactoring affects template files across multiple modules including account, board, CRM, HR, and many others, converting patterns like "showUploadButton" to "this.showUploadButton" and "state.name" to "this.state.name" throughout XML templates.
[IMP] *: run rendering context migration script entire codebase
2026-03-20
The MRP module's production order tracking was refactored to use the new unified '_track_add' tool instead of custom low-level tracking code for the date_finished field changes on completed productions. This simplifies maintenance by leveraging standardized tracking infrastructure while preserving the same business functionality of recording when production completion dates are modified.
[REF] mrp: replace manual track
This commit adds test coverage for the manual tracking of date_finished field changes on manufacturing orders in Odoo MRP. The test verifies that when the date_finished is modified without changing the production order state, the system correctly records and tracks this change with proper tracking values logged to the mail message history. This ensures that future modifications to the tracking model will not break the date_finished change tracking functionality.
[IMP] mrp: test date_finished manual tracking
2026-03-19
2026-03-17
[REF] *: migrate type="base64" to "bytes"