| Created Date | Type | Name | Commit Description | State | Age | Up Time | Life Time | Action |
|---|---|---|---|---|---|---|---|---|
|
merged
Merge from upstream 16 20250701 01
|
Succeed | ||||||
|
|
merged
[PERF] mrp: optimize move_finished_ids update to improve backorder creation performance for serial-tracked production
|
[PERF] mrp: optimize move_finished_ids update to improve backorder creation performance for serial-tracked production Previously, all move_finished_ids in non-done state were updated regardless of whether their date or date_deadline values actually changed. This led to unnecessary write operations and potential slowdowns, especially in serial-tracked production where each finished product line generates a separate stock.move. This update improves the performance of completing manufacturing orders that produce serial-tracked finished products. | Succeed | |||||
|
|
merged
[IMP] stock: Improve query of move_orig_ids and move_dest_ids
|
[IMP] stock: Improve query of move_orig_ids and move_dest_ids | Failed | Not finished | ||||
|
|
merged
[IMP] stock: Improve query of move_orig_ids and move_dest_ids
|
[IMP] stock: Improve query of move_orig_ids and move_dest_ids | Killed | Not started | Not finished | |||
|
|
merged
[IMP][16.0] mrp*: Improved speed when viewing production orders
|
[PERF] purchase_mrp: optimize purchase_order_count computation using single SQL query The previous approach used multiple ORM traversals and len(set(...)) logic in Python, which caused performance degradation on large datasets. This PR improves the performance of the purchase_order_count computed field on the production order by replacing the slow Python-level iteration over stock moves with a single optimized SQL query. This refactor ensures fast and reliable results even on databases with thousands of stock moves and procurement groups. | Killed | Not started | Not finished | |||
|
|
merged
[IMP][16.0] mrp*: Improved speed when viewing production orders
|
[IMP] mrp*: Improved speed when viewing production orders In cases where the production order has been done or canceled, it is not necessary to recalculate. This significantly improves the speed of opening production orders, especially for production orders with backorders. | Killed | |||||
|
|
merged
[IMP][16.0] mrp*: Improved speed when viewing production orders
|
[IMP] mrp*: Improved speed when viewing production orders In cases where the production order has been done or canceled, it is not necessary to recalculate. This significantly improves the speed of opening production orders, especially for production orders with backorders. | Killed | Not finished | ||||
|
|
merged
[IMP][16.0] mrp*: Improved speed when viewing production orders
|
[IMP] mrp*: Improved speed when viewing production orders In cases where the production order has been done or canceled, it is not necessary to recalculate. This significantly improves the speed of opening production orders, especially for production orders with backorders. | Killed | Not finished | ||||
|
|
merged
[IMP][16.0] mrp*: Improved speed when viewing production orders
|
[IMP] mrp*: Improved speed when viewing production orders In cases where the production order has been done or canceled, it is not necessary to recalculate. This significantly improves the speed of opening production orders, especially for production orders with backorders. | Killed | Not started | Not finished | |||
|
|
merged
[IMP][16.0] mrp*: Improved speed when viewing production orders
|
[IMP] mrp*: Improved speed when viewing production orders In cases where the production order has been done or canceled, it is not necessary to recalculate. This significantly improves the speed of opening production orders, especially for production orders with backorders. | Killed | Not finished | ||||
|
|
open
[I18N][16.0] base: correct Vietnamese translation in contact
|
[I18N] base: correct Vietnamese translation in contact | Killed | |||||
|
|
open
[I18N][16.0] stock: correct Vietnamese translation in stock
|
[I18N] stock: correct Vietnamese translation in stock Signed-off-by: TuyenTran <trandinhtuyen2018@gmail.com> | Killed | |||||
|
|
merged
[I18N] auth_ldap
|
[I18N] auth_ldap | Killed | Not started | Not finished | |||
|
|
closed
[IMP] *: optimize ORM cache handling
|
[IMP] *: optimize ORM cache handling Updated multiple models to improve performance by preventing unnecessary ORM cache clearing. This change applies to the AutomaticEntryWizard, GoogleSync, MicrosoftSync and Employee models, ensuring more efficient data handling during write operations. | Killed | |||||
|
|
closed
[IMP] *: optimize ORM cache handling
|
[IMP] *: optimize ORM cache handling Updated multiple models to improve performance by preventing unnecessary ORM cache clearing. This change applies to the AutomaticEntryWizard, GoogleSync, MicrosoftSync and Employee models, ensuring more efficient data handling during write operations. | Killed | |||||
|
|
closed
[IMP] *: optimize ORM cache handling
|
[IMP] *: optimize ORM cache handling Updated multiple models to improve performance by preventing unnecessary ORM cache clearing. This change applies to the AutomaticEntryWizard, GoogleSync, MicrosoftSync and Employee models, ensuring more efficient data handling during write operations. | Killed | Not finished | ||||
|
|
closed
[IMP] *: optimize ORM cache handling
|
[IMP] account, google_calendar, hr_presence: optimize ORM cache handling Updated multiple models to use 'with_context(skip_clear_ormcache=True)' for specific record updates, improving performance by preventing unnecessary ORM cache clearing. This change applies to the AutomaticEntryWizard, GoogleSync, and Employee models, ensuring more efficient data handling during write operations. | Killed | |||||
|
|
open
[FIX][16.0] stock_account: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains
|
[FIX][16.0] stock_account: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains | Killed | |||||
|
|
merged
[I18N][16.0] base: correct vietnamese translation in contact
|
[I18N] base: correct vietnamese translation in contact | Killed | |||||
|
|
merged
Merge from upstream 16 20250701 01
|
Merge remote-tracking branch 'odoo/16.0' into 16.0 | Killed | |||||
|
|
merged
Merge from upstream 16 20250604 01
|
Merge remote-tracking branch 'odoo/16.0' into 16.0 Conflicts: addons/account/i18n/vi.po addons/account_check_printing/i18n/vi.po addons/auth_oauth/i18n/vi.po addons/barcodes/i18n/vi.po addons/barcodes_gs1_nomenclature/i18n/vi.po addons/calendar/i18n/vi.po addons/crm_iap_enrich/i18n/vi.po addons/crm_livechat/i18n/vi.po addons/event/i18n/vi.po addons/fleet/i18n/vi.po addons/gamification/i18n/vi.po addons/google_calendar/i18n/vi.po addons/google_gmail/i18n/vi.po addons/hr/i18n/vi.po addons/hr_attendance/i18n/vi.po addons/hr_contract/i18n/vi.po addons/hr_expense/i18n/vi.po addons/hr_fleet/i18n/vi.po addons/hr_holidays/i18n/vi.po addons/hr_holidays_attendance/i18n/vi.po addons/hr_timesheet_attendance/i18n/vi.po addons/hr_work_entry/i18n/vi.po addons/im_livechat/i18n/vi.po addons/link_tracker/i18n/vi.po addons/mail/i18n/vi.po addons/maintenance/i18n/vi.po addons/mass_mailing/i18n/vi.po addons/microsoft_calendar/i18n/vi.po addons/microsoft_outlook/i18n/vi.po addons/mrp/i18n/vi.po addons/mrp_subcontracting/i18n/vi.po addons/phone_validation/i18n/vi.po addons/point_of_sale/i18n/vi.po addons/product/i18n/vi.po addons/project/i18n/vi.po addons/purchase/i18n/vi.po addons/purchase_stock/i18n/vi.po addons/resource/i18n/vi.po addons/sale/i18n/vi.po addons/sale_crm/i18n/vi.po addons/sale_expense/i18n/vi.po addons/sale_management/i18n/vi.po addons/sale_stock/i18n/vi.po addons/spreadsheet_dashboard_im_livechat/i18n/vi.po addons/stock/i18n/vi.po addons/stock_account/i18n/vi.po addons/stock_picking_batch/i18n/vi.po addons/survey/i18n/vi.po addons/web_editor/i18n/vi.po addons/website/i18n/vi.po addons/website_event_questions/i18n/vi.po addons/website_forum/i18n/vi.po addons/website_mass_mailing/i18n/vi.po addons/website_sale/i18n/vi.po addons/website_slides/i18n/vi.po odoo/addons/base/i18n/vi.po | Failed | |||||
|
|
merged
[I18N][16.0] base: correct vietnamese translation in contact
|
[I18N] base: correct vietnamese translation in contact | Killed | |||||
|
|
merged
[I18N][16.0] base: correct vietnamese translation in contact
|
[I18N] base: correct vietnamese translation in contact | Killed | |||||
|
|
closed
[I18N][16.0] base: correct vietnamese translation in contact
|
[FIX] product: Fix type in product filter **Reason** - Using type as filter is not efficient since user tend to look for what category that product is, change to detailed_type | Killed | Not finished | ||||
|
|
merged
[IMP] product_margin: improve Product Margins report performance by filtering products based on selected invoices in the wizard
|
[IMP] product_margin: improve Product Margins report performance by filtering products based on selected invoices in the wizard The Product Margins report currently loads all products, which leads to major performance issues or timeouts when working with large datasets (e.g., over 200,000 products). This PR modifies the logic to only load products that are referenced in invoices within the selected date range and invoice state in the wizard. | Killed | |||||
|
|
open
[FIX][16.0] stock_account: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains
|
[FIX] purchase: Incorrectly recorded product unit price due to rounding Issue: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains. Steps to reproduce the error: 1. Setup company with Rounding Factor currency 1, for example VND 1. Create product A, Costing Method: AVCO 2. Enter purchase order 10 units of product A with unit price 1.46 3. Create sales order with quantity 12 units of product A 4. Enter 2 units of product with price 1.46 View stock layer, stock quantity is 0 but stock value is 1. This is unexpected. | Killed | |||||
|
|
open
[FIX][16.0] stock_account: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains
|
[FIX] purchase: Incorrectly recorded product unit price due to rounding Issue: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains. Steps to reproduce the error: 1. Setup company with Rounding Factor currency 1, for example VND 1. Create product A, Costing Method: AVCO 2. Enter purchase order 10 units of product A with unit price 1.46 3. Create sales order with quantity 12 units of product A 4. Enter 2 units of product with price 1.46 View stock layer, stock quantity is 0 but stock value is 1. This is unexpected. | Killed | Not finished | ||||
|
|
open
[FIX][16.0] stock_account: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains
|
Killed | ||||||
|
|
open
[FIX][16.0] stock_account: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains
|
[FIX] stock: Unit price rounding error Issue: Rounding error when calculating unit price causes the quantity of goods to be out of stock but the inventory value still remains. Steps to reproduce the error: 1. Setup company with Rounding Factor currency 1, for example VND 1. Create product A, Costing Method: AVCO 2. Enter purchase order 10 units of product A with unit price $1.46 3. Create sales order with quantity 12 units of product A 4. Enter 2 units of product with price $1.46 View stock layer, stock quantity is 0 but stock value is 1. This is unexpected. | Killed | Not finished | ||||
|
|
closed
[I18N][16.0] base: correct vietnamese translation in contact
|
[I18N] base: correct vietnamese translation in contact | Killed | |||||
|
|
merged
Merge from upstream 16 20250303 01
|
Failed | ||||||
|
|
merged
[FIX] loyalty: default product for reward in multi company
|
[FIX] loyalty: default product for reward in multi company Steps to reproduce: ------------------- - being in a multi-company environment; - have one product made that is first in alphabetical order of "Internal Reference" throughout the database (e.g. [AAA]); - make this product specific to one of the companies (set the "Company" field on the product template) - go into a different company within the database (not the one set on this product); - create a new discount & loyalty record, and set the "Program Type" to "Discount Code". Issue: ------ An access rights error occurs. Cause: ------ When creating a `promo_code` program, we use the first product that can be sold in the default reward values. Solution: --------- Take into account the company in the domain that retrieves the default product. | Killed | Not started | Not finished | |||
|
|
merged
Merge from upstream 16 20250218 01
|
Merge remote-tracking branch 'odoo/16.0' into 16.0 | Killed | |||||
|
|
merged
[FIX] point_of_sale: ensuring the correct removal from self.syncingOrders
|
[FIX] point_of_sale: ensuring the correct removal from self.syncingOrders Previously, the code attempted to delete an element using order_id, but ordersToSync is an array of order objects, not order IDs. The fix updates the loop to use order.id instead of order_id, ensuring the correct removal from self.syncingOrders. | Killed | Not started | Not finished | |||
|
|
merged
Revert "[FIX] point_of_sale: remove raise to continue processing other orders on failure"
|
Revert "[FIX] point_of_sale: remove raise to continue processing other orders on failure" This reverts commit f2f646aa7b47c279de5c48e81f5dfd849e2078c7. | Killed | Not started | Not finished | |||
|
|
merged
Merge from upstream 16 20250212 01
|
Merge remote-tracking branch 'odoo/16.0' into 16.0 | Failed | |||||
|
|
merged
[FIX] point_of_sale: avoid singleton error when using search product
|
[FIX] point_of_sale: avoid singleton error when using search product | Failed | |||||
|
|
merged
[FIX] point_of_sale: remove raise to continue processing other orders on failure
|
[FIX] point_of_sale: remove raise to continue processing other orders on failure Previously, if a PoS order failed during synchronization from the frontend, the entire process stopped due to the raise statement in the except block. This PR removes raise, allowing the system to continue processing the remaining orders even if some fail. Failed orders will still be logged and an activity will be created for later handling. This ensures that valid orders are not affected by individual failures, improving performance and user experience during data synchronization. | Killed | |||||
|
|
merged
Merge from upstream 16 20250204 01
|
Merge remote-tracking branch 'odoo/16.0' into 16.0 | Killed | |||||
|
|
merged
Merge from upstream 16 20250204 01
|
[I18N] account, sale_loyalty_delivery: fix format string | Killed |
