Monday, November 18, 2024
17 changes · 18.0
Enhancements to existing features
The stock search view keeps common nearby-date filters visible so users can quickly find relevant warehouse operations. This makes day-to-day inventory checks easier without needing to dig through hidden search options.
Original PR description
The filters has been added to work with the graph overview. However people asks to not hide everything in the search since it's a basic operation Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Dragging a signing field from the sidebar now shows a preview that matches the final dropped size. This makes document preparation smoother and avoids confusing size changes when placing signature fields.
Original PR description
Before this commit, when onSidebarDragStart was called to start dragging a sign item from the side bar, the placeholder was not resized the same it it is when it is dropped. Therefore the placeholder would see his change change upon releasing the element. taskid: 4164114
When sending a message about a salary offer, the system now automatically suggests the email address of the related employee or applicant. This helps HR teams send offer communications faster and reduces the chance of choosing the wrong recipient.
Original PR description
Offer "send message" will directly propose the email of the offer's employee/applicant. task-4062860
Resolved issues and error corrections
This update prevents a restaurant point-of-sale automated test from failing when a failed-printing pop-up appears. By closing that pop-up before continuing, the test flow becomes more stable and reduces false failures during quality checks.
Original PR description
In this commit, we ensure to close modal (failed printing) before continue the tour or it can cause failures in tour. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Versions -------- - saas-17.4+ Steps ----- Try to pay with saved payment method. Issue ----- > The payment has been declined: Authentication required. > The financial institution insists on 3-D Secure. Cause ----- Bank may insist on 3-D Secure authentication, failing the payment transaction, which isn't handled in the `payment_token` flow. Solution -------- If 3-D Secure authentication is requested, reset transaction to draft, and attempt redirect flow. > [!Note] > Doe
Original PR description
Versions -------- - saas-17.4+ Steps ----- Try to pay with saved payment method. Issue ----- > The payment has been declined: Authentication required. > The financial institution insists on 3-D Secure. Cause ----- Bank may insist on 3-D Secure authentication, failing the payment transaction, which isn't handled in the `payment_token` flow. Solution -------- If 3-D Secure authentication is requested, reset transaction to draft, and attempt redirect flow. > [!Note] > Doesn't work for automated payments (subscriptions). opw-4223022 Forward-Port-Of: odoo/odoo#184710
The mail GIF picker now handles duplicate category names from external GIF data, which could previously cause a crash in some languages such as Portuguese. This improves reliability for users adding GIFs in discussions without changing the visible feature set.
Original PR description
Before this commit, opening of GIF picker in some languages like Portuguese could lead to following crash: ``` OwlError: Got duplicate key in t-foreach: #irritado ``` This happens because GIF picker categories come from Tenor data and there might be duplicated categories. However in code we use `category.name` for `t-key`, thus there was a crash when 2 categories had the same name. This commit fixes the issue by using `category_index` instead, which is the index of category in the global list of categories, which is necessarily unique for each GIF category. opw-4319241
This change updates documentation links across Odoo so they point to the correct 18.0 documentation instead of older or generic versions. It helps users and administrators reach the right guidance for their current Odoo version, reducing confusion when following help links.
Original PR description
same like https://github.com/odoo/odoo/pull/141406 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Trial Balance report now correctly displays ending balance amounts when the "Blank if Zero" option is enabled. This prevents non-zero ending balances from being hidden on lines that only have debit or only have credit activity, improving report accuracy for finance users.
Original PR description
To reproduce: - Edit 'Trial Balance' report and enable the "Blank if Zero" option for both debit and credit lines - Open a 'Trial Balance', observe there is no 'End Balance' values for line where there are only debit or only credit amounts. This commit also update the `is_zero` option for end balance columns value to ensure there are correctly shown when "Blank if Zero" option is enabled.
This fixes an error in Colombian online checkout when customers edit a delivery address that is also used for billing. The checkout now shows the required obligation type information in that case, helping customers complete purchases without interruption.
Original PR description
Steps to reproduce: 1. Create a store with Colombian localization. 2. Go to the shop and select any product. 3. Proceed to checkout and try to edit the delivery address. An error occurs when editing the delivery address because the `obligation_types` field is NULL. The issue is caused by the condition in the template ([link to the condition]), which checks only if `address_type` is 'billing'. However, the address type can be 'delivery' when using the delivery address as the billing address, resulting in a null reference in the DOM for the obligation types element. I Updated the condition to check for `(address_type == 'billing' or use_delivery_as_billing)`, ensuring that the obligation types element is displayed correctly when the delivery address is used as the billing address. opw-4309448
This update prevents an error during checkout for Colombian online stores when customers edit a delivery address that is also used for billing. It ensures the required tax obligation information appears in the right situation, helping customers complete purchases without interruption.
Original PR description
Steps to reproduce: 1. Create a store with Colombian localization. 2. Go to the shop and select any product. 3. Proceed to checkout and try to edit the delivery address. An error occurs when editing the delivery address because the `obligation_types` field is NULL. The issue is caused by the condition in the template ([link to the condition]), which checks only if `address_type` is 'billing'. However, the address type can be 'delivery' when using the delivery address as the billing address, resulting in a null reference in the DOM for the obligation types element. Solution: Updated the condition to check for `(address_type == 'billing' or use_delivery_as_billing)`, ensuring that the obligation types element is displayed correctly when the delivery address is used as the billing address. opw-4309448
This change fixes an automated check for the restaurant preparation display by preventing an unrelated printer error message from appearing during the test. It helps keep quality checks stable so future updates can be validated with fewer false failures.
Original PR description
Fix tour test_03_preparation_display_skip_change by unlink printer config to avoid the appear of modal "printing failed".
This update adjusts an automated restaurant preparation display test so it no longer triggers an unrelated printing failure message. This helps keep quality checks stable and reduces false alarms during development.
Original PR description
Fix tour test_03_preparation_display_skip_change by unlink printer config to avoid the appear of modal "printing failed".
Before this commit, when changing the chart type, the data source was not updated. Which was a problem, because the data returned for different chart types is different (eg. pie charts filter empty points). That meant that when changing the chart type from line => pie we displayed a pie with empty points, but when reloading the page the data would change to the correct one. Task: [4306227](https://www.odoo.com/web#id=4306227&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&
Original PR description
Before this commit, when changing the chart type, the data source was not updated. Which was a problem, because the data returned for different chart types is different (eg. pie charts filter empty points). That meant that when changing the chart type from line => pie we displayed a pie with empty points, but when reloading the page the data would change to the correct one. Task: [4306227](https://www.odoo.com/web#id=4306227&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186810 Forward-Port-Of: odoo/odoo#186110
A traceback occurs when the user tries to filter stock quants by on-hand, if there is no warehouse. To reproduce this issue: 1) Install stock without demo 2) Archive the warehouse 3) Open physical Inventory from operations 4) Filter it through `On-Hand` through the Toggle Search Panel Error:- ``` AttributeError: 'int' object has no attribute 'startswith' ``` When the user archived the warehouse, we get the `domain_loc` as `[(0, '=', 1)]` at line [2]. This is because there is
Original PR description
A traceback occurs when the user tries to filter stock quants by on-hand, if there is no warehouse. To reproduce this issue: 1) Install stock without demo 2) Archive the warehouse 3) Open physical…
A traceback occurs when the user tries to filter stock quants by on-hand, if there is no warehouse. To reproduce this issue: 1) Install stock without demo 2) Archive the warehouse 3) Open physical Inventory from operations 4) Filter it through `On-Hand` through the Toggle Search Panel Error:- ``` AttributeError: 'int' object has no attribute 'startswith' ``` When the user archived the warehouse, we get the `domain_loc` as `[(0, '=', 1)]` at line [2]. This is because there is no location, as the location is derived from the warehouse. If there is no location, it returns three times of`[(0, '=', 1)]` from [1] [1] https://github.com/odoo/odoo/blob/9ce9c6d0d815dcf8fd97fdab484872a607579bd5/addons/stock/models/product.py#L309-L310 [2] https://github.com/odoo/odoo/blob/9ce9c6d0d815dcf8fd97fdab484872a607579bd5/addons/stock/models/stock_quant.py#L240-L241 This leads to the above traceback when `startswith` is used on the first value of the domain which is an integer. https://github.com/odoo/odoo/blob/9ce9c6d0d815dcf8fd97fdab484872a607579bd5/addons/stock/models/stock_quant.py#L180-L184 sentry-6016230486 Forward-Port-Of: odoo/odoo#185628
Steps: - Create a dynamic attribute with some attribute Lines - Create a product with attributes set to the new attribute - Change cost price and save - Reload the webpage Issue: - Cost price changes back to 0 Cause: - `_compute_template_field_from_variant_field` is called on `_compute_standard_price` which sets the value of field to default (false) for variant_count=0 Fix: - Cost price will be invisible for variant_count=0 (only on saved records, to allow products with non-dynam
Original PR description
Steps: - Create a dynamic attribute with some attribute Lines - Create a product with attributes set to the new attribute - Change cost price and save - Reload the webpage Issue: - Cost price changes back to 0 Cause: - `_compute_template_field_from_variant_field` is called on `_compute_standard_price` which sets the value of field to default (false) for variant_count=0 Fix: - Cost price will be invisible for variant_count=0 (only on saved records, to allow products with non-dynamic attributes to still be configured directly on creation). opw-4054647 Forward-Port-Of: odoo/odoo#187308 Forward-Port-Of: odoo/odoo#181836
Sales order created from purchase orders thanks to the inter-company module were assigned the default team of the company, regardless of the customer configuration. This commit makes sure the team is correctly computed in the dedicated compute, ensuring the expected team is assigned to the Sales Order. opw-4166598 Forward-Port-Of: odoo/enterprise#72767
Original PR description
Sales order created from purchase orders thanks to the inter-company module were assigned the default team of the company, regardless of the customer configuration. This commit makes sure the team is correctly computed in the dedicated compute, ensuring the expected team is assigned to the Sales Order. opw-4166598 Forward-Port-Of: odoo/enterprise#72767
When opening a validated quality check from a MO/WO, if the type of the quality check is 'picture', the QC wizard should show the image taken. Forward-Port-Of: odoo/enterprise#73561
Original PR description
When opening a validated quality check from a MO/WO, if the type of the quality check is 'picture', the QC wizard should show the image taken. Forward-Port-Of: odoo/enterprise#73561