| Created Date | Type | Name | Commit Description | State | Age | Up Time | Life Time | Action |
|---|---|---|---|---|---|---|---|---|
|
open
[I18N][17.0] point_of_sale: fix i18n
|
[I18N] point_of_sale: fix i18n | Killed | |||||
|
|
open
[FIX][17.0] hr_recruitment: Fix permissions error
|
[FIX] hr_recruitment: Fix permissions error This comment is to fix the bug where the user only had HR privileges when viewing the hr.job model interface, resulting in an error message indicating no permission to read hr.applicant. | Killed | |||||
|
|
merged
Merge from upstream 17 20260110 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
open
[FWD][17.0][I18N] purchase_stock: correct Vietnamese translation
|
[I18N] purchase_stock: correct Vietnamese translation Forward-Port-Of: #1170 | Revoked | |||||
|
|
closed
[FWD][17.0] mail: fix incorrect avatar display
|
[FIX] mail: fix incorrect avatar display Before this commit, user avatars in the Chater UI were not displayed using the object-fit: cover style, causing distorted or improperly scaled images. closes odoo/odoo#242320 Signed-off-by: Alexandre Kühn (aku) <aku@odoo.com> | Killed | |||||
|
|
merged
Merged from upstream 17 260104 01
|
Merge remote-tracking branch 'upstream/17.0' into 17.0 | Killed | |||||
|
|
merged
[FWD][17.0][I18N] stock: fix i18n stock
|
[I18N] *: fix i18n stock, purchase Forward-Port-Of: #1163 | Failed | |||||
|
|
merged
[FIX][17.0] hr_org_chart: Do not display employees
|
[FIX] hr_org_chart: Do not display employees | Killed | |||||
|
|
merged
[FIX][17.0] hr_org_chart: Do not display employees
|
[FIX] hr_org_chart: Do not display employees | Killed | Not started | Not finished | |||
|
|
merged
Merge from upstream 17 20251220 01
|
Killed | ||||||
|
|
merged
Merge from upstream 17 20251220 01
|
Merge remote-tracking branch 'odoo/17.0' into merge_from_upstream_17_20251220_01 | Killed | |||||
|
|
merged
Merge from upstream 17 20251219 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
[I18N] hr: correct Vietnamese department name
|
Killed | ||||||
|
|
merged
Merge from upstream 17 20251211 01
|
Killed | ||||||
|
|
merged
[PERF] pos_sale: optimize Session Sale Amount compute by pre-fetching
|
[PERF] pos_sale: optimize Session Sale Amount compute by pre-fetching opened sessions to avoid heavy subquery execution Problem The original implementation performs a _read_group on report.pos.order with a domain that includes a relational lookup: ('session_id.state', '=', 'opened') On large databases, this condition forces the ORM to generate a SQL query containing nested subqueries like: session_id IN (SELECT id FROM pos_session WHERE state='opened' AND ...) PostgreSQL cannot short-circuit this subquery, even if no sessions are opened, and still scans a large portion of report_pos_order, causing significant performance degradation. Solution Instead of letting _read_group build a heavy subquery, we explicitly search for the opened sessions first: opened_sessions = self.env['pos.session'].search([ ('config_id.crm_team_id', 'in', self.ids), ('state', '=', 'opened'), ]) data = self.env['report.pos.order']._read_group([ ('session_id', 'in', opened_sessions.ids), ], ['config_id'], ['price_total:sum']) This improves performance because: pos.session is a much smaller table and is fast to filter. If there are no opened sessions, _read_group immediately returns empty results without scanning report_pos_order. It eliminates nested SQL IN (SELECT ...), allowing PostgreSQL to use direct index-based filtering. This approach reduces query time dramatically on large datasets. | Killed | |||||
|
|
closed
17.0
|
[FIX] stock: Allow to install demo data outside US company Currently in the `_merge_move_itemgetter` the system call `self.company_id.currency_id.decimal_places`. However the demo data of stock create a database with US currency and some `stock.move` in it. If we have an existing database with EUR for example. The upper call will return a `currency_id.decimal_places` since we have multiple currency. The best solution, would be to split `_action_confirm` to do a loop by company. But it would need a small refactoring and we will do a minimal diff to fix this issue. Using the smallest currency among all the company is not always correct but it's a super edge case and we should probably remove this code since it went to far. Close #230965, #234078 closes odoo/odoo#239273 Signed-off-by: William Henrotin (whe) <whe@odoo.com> | Killed | Not started | Not finished | |||
|
|
merged
Merge from upstream 17 20251211 01
|
Merge remote-tracking branch 'odoo/17.0' into merge_from_upstream_17_20251205_01 | Killed | |||||
|
|
merged
Merge from upstream 17 20251211 01
|
Merge remote-tracking branch 'odoo/17.0' into merge_from_upstream_17_20251205_01 | Killed | |||||
|
|
merged
[FIX] web_editor, mail, account_edi: add indexes to improve performance when deleting ir_attachment records
|
[FIX] web_editor, mail, account_edi: add indexes to improve performance when deleting ir_attachment records On a DB with 15M+ attachments, deleting a single attachment takes several seconds. Most of the time is spent on the circular `original_id` and `message_main_attachment_id` foreign key. | Killed | |||||
|
|
merged
[IMP] base_import_module: Log traceback when upload module failed
|
Killed | ||||||
|
|
merged
[IMP] base_import_module: Log traceback when upload module failed
|
Killed | Not started | Not finished | ||||
|
|
merged
Merge from upstream 17 20251117 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20251117 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20251113 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20251111 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20250111 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20251028 01
|
Killed | ||||||
|
|
merged
Merge from upstream 17 20251028 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20251028 01
|
Merge remote-tracking branch 'odoo/17.0' into merge_from_upstream_17_20251028_01 | Killed | |||||
|
|
merged
Merge from upstream 17 20251001 01
|
Killed | ||||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
[IMP] web: formatCurrency for kanban header data if group field is currency | Killed | |||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
Killed | Not finished | |||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
Killed | Not finished | |||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
Killed | ||||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
Killed | Not started | Not finished | ||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
Killed | Not finished | |||||
|
|
merged
[IMP][17.0] web: formatCurrency for kanban header data if group field is cu…
|
[IMP] web: formatCurrency for kanban header data if group field is currency | Killed | |||||
|
|
merged
[FIX] mail: remove stale followers from chatter on auto-unfollow
|
[FIX] mail: remove stale followers from chatter on auto-unfollow In a customized flow: when reassigning a Ticket from employee A to B, the code unsubscribes A and subscribes B automatically. However, A still appears in the Chatter Followers list even after the unsubscribe call. | Killed | |||||
|
|
merged
Merge from upstream 17 20251001 01
|
Merge remote-tracking branch 'odoo/17.0' into 17.0 | Killed | |||||
|
|
merged
Merge from upstream 17 20251001 01
|
Merge remote-tracking branch 'odoo/17.0' into merge_from_upstream_17_20251001_01 | Killed |
