Wednesday, November 6, 2024
33 changes · saas-17.4
Resolved issues and error corrections
This fixes an error that appeared when someone opened a cancelled signing request and landed on the expected 404 page. The website now avoids running image zoom behavior when there are no zoomable elements, preventing an unnecessary technical traceback.
Original PR description
Steps to reproduce: - Sign app > Upload PDF > Add a 'Signature' field > Send > Cancel - In mailhog open the email > Click 'Sign Document' - Redirected to 404 as expected - Traceback '$(...).zoomOdoo is not a function' No zoomable elements are found by JQuery on the 404 redirection page, meaning the functions which assume such an element must exist cause an error. The option to cancel sign requests is available in saas-17.4 and above only. opw-4261794 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoice previews for the Chilean localization now keep long document type labels within the visible page area. This prevents the document type border from extending outside its container, improving the appearance of generated invoices.
Original PR description
[FIX] l10n_cl: display the document type border correctly Steps to reproduce: 1 - In the chilean localization create an invoice (with a long text document type). 2 - Preview The observed behaviour: - The right side of the border of the document type would go out of the view. This Fix would just make the maximum width of the said border to never exceed its container. opw-4278374 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Planning app toast shown when asking someone to switch now displays its status icons clearly. This removes a visual issue where confirmation and warning icons blended into the toast background, making the message easier to understand.
Original PR description
Currently, when the "Ask to Switch" toast is displayed, the fa-check-circle and fa-exclamation-circle are not visible because they have the same color as the background of the toast. This PR will remove their color, making them dark and visible. task-3919543
Miscellaneous changes
Issue: When printing an employee badge for an employee without a job position, the default title was set to "Software Developer." Steps to Reproduce: -Create an employee with an empty job position. -Alternatively, remove the job position of an existing employee. -Generate and print a badge (in HR settings). Explanation: In `hr_employee_badge.xml`, the default value was set to "Software Developer." opw-4255102 --- I confirm I have signed the CLA and read the PR guidelines at www.
Original PR description
Issue: When printing an employee badge for an employee without a job position, the default title was set to "Software Developer." Steps to Reproduce: -Create an employee with an empty job position. -Alternatively, remove the job position of an existing employee. -Generate and print a badge (in HR settings). Explanation: In `hr_employee_badge.xml`, the default value was set to "Software Developer." opw-4255102 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#185458
Steps to reproduce: - Drag and drop any snippet with image in it. - Select image and crop image using transform option. - Click replace button. - Image selection popover won't open. After this commit: - The "preserveCursor" method has been used to maintain the cursor state because transform option was losing cursor selection. task-3930743 Forward-Port-Of: odoo/odoo#167338
Original PR description
Steps to reproduce: - Drag and drop any snippet with image in it. - Select image and crop image using transform option. - Click replace button. - Image selection popover won't open. After this commit: - The "preserveCursor" method has been used to maintain the cursor state because transform option was losing cursor selection. task-3930743 Forward-Port-Of: odoo/odoo#167338
This PR updates l10n_uy by adding 22% and 10% VAT-included tax options for sales and purchases, supporting Uruguay’s practice of using both tax-included and tax-excluded amounts per document. The data aligns with XML requirements by specifying VAT inclusion at the document level, enabling accurate automatic vendor bill creation from XML imports. Task Adhoc side: 43467 Task latam side: 1282 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forwa
Original PR description
This PR updates l10n_uy by adding 22% and 10% VAT-included tax options for sales and purchases, supporting Uruguay’s practice of using both tax-included and tax-excluded amounts per document. The data aligns with XML requirements by specifying VAT inclusion at the document level, enabling accurate automatic vendor bill creation from XML imports. Task Adhoc side: 43467 Task latam side: 1282 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#184940
Since #138471, each time `create_or_update_sequences_and_picking_types` is called, the related sequences will be updated to their default values. This means that if a user changed the sequence_code of a standard picking type, whenever that method is called (which can happen at the update of a warehouse), it will erase their settings. Rather than that, if the picking type already exist, we use its sequence_code instead of the default one. Related to: opw-4245938 opw-4264520 --- I conf
Original PR description
Since #138471, each time `create_or_update_sequences_and_picking_types` is called, the related sequences will be updated to their default values. This means that if a user changed the sequence_code of a standard picking type, whenever that method is called (which can happen at the update of a warehouse), it will erase their settings. Rather than that, if the picking type already exist, we use its sequence_code instead of the default one. Related to: opw-4245938 opw-4264520 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186051 Forward-Port-Of: odoo/odoo#185966
Versions -------- - 16.0 _(sale_product_configurator)_ - 17.0+ _(website_sale_product_configurator)_ Steps ----- 1. Enable Dutch language; 2. go to eCommerce; 3. switch to mobile view; 4. go to a product which has optional products; 5. add to cart. Issue ----- There's not enough space in the configurator to properly display the "Toevoegen aan winkelmandje" button. Cause ----- The view isn't mobile-responsive. Solution -------- 16.0 up to 17.2: - Replace the button wi
Original PR description
Versions -------- - 16.0 _(sale_product_configurator)_ - 17.0+ _(website_sale_product_configurator)_ Steps ----- 1. Enable Dutch language; 2. go to eCommerce; 3. switch to mobile view; 4. go to a product which has optional products; 5. add to cart. Issue ----- There's not enough space in the configurator to properly display the "Toevoegen aan winkelmandje" button. Cause ----- The view isn't mobile-responsive. Solution -------- 16.0 up to 17.2: - Replace the button with a simple cart icon to ensure consistency between localisations while keeping things simple. saas-17.4 up to master: - Replace the '+' icon with a shopping cart for eCommerce. - Instead of hiding the icon on mobile, hide the text. opw-4198786 Forward-Port-Of: odoo/odoo#185936 Forward-Port-Of: odoo/odoo#185133
When an exception occurred during a request to IAP, there was no way of knowing which one it was exactly. This log should help understand what went wrong. Related ticket for which this would have been helpful: #4276907 Forward-Port-Of: odoo/odoo#185535
Original PR description
When an exception occurred during a request to IAP, there was no way of knowing which one it was exactly. This log should help understand what went wrong. Related ticket for which this would have been helpful: #4276907 Forward-Port-Of: odoo/odoo#185535
Steps to reproduce the bug: - Create a storable product “P1”: - tracked by serial number - Update the quantity with SN1 - Create a delivery: - Customer: Azure Interior - Product: P1 with SN1 - Validate the delivery - Create a return to WH/Stock and validate it - Go to the serial number Problem: The location is not updated and displays the partner location instead of WH/Stock. opw-4285271 Forward-Port-Of: odoo/odoo#186067 Forward-Port-Of: odoo/odoo#185917
Original PR description
Steps to reproduce the bug:
- Create a storable product “P1”:
- tracked by serial number
- Update the quantity with SN1
- Create a delivery:
- Customer: Azure Interior
- Product: P1 with SN1
- Validate the delivery
- Create a return to WH/Stock and validate it
- Go to the serial number
Problem:
The location is not updated and displays the partner location instead of WH/Stock.
opw-4285271
Forward-Port-Of: odoo/odoo#186067
Forward-Port-Of: odoo/odoo#185917Steps: - Open Terminal and click on the burger combo - Select burger and click the cancel button - Select the burger again and click OK with the default selection - Select a drink Issue: - After selecting all components of the product, the `Add to Order` button remains disabled, preventing the combo from being added to the cart. Cause: - The combo state is not being reset when discarding or closing the product configuration popup. Fix: - Implemented a proper reset of the combo st
Original PR description
Steps: - Open Terminal and click on the burger combo - Select burger and click the cancel button - Select the burger again and click OK with the default selection - Select a drink Issue: - After selecting all components of the product, the `Add to Order` button remains disabled, preventing the combo from being added to the cart. Cause: - The combo state is not being reset when discarding or closing the product configuration popup. Fix: - Implemented a proper reset of the combo state upon closing the configuration popup. task-4285981 Forward-Port-Of: odoo/odoo#186274 Forward-Port-Of: odoo/odoo#185296
The grid layout in attachment list makes the non attachment list view look broken. This commit removes the grid from this view. Steps to reproduce: - open a discuss channel - add some non image attachments - go to the attachments list Backport of https://github.com/odoo/odoo/pull/186033 Forward-Port-Of: odoo/odoo#186364
Original PR description
The grid layout in attachment list makes the non attachment list view look broken. This commit removes the grid from this view. Steps to reproduce: - open a discuss channel - add some non image attachments - go to the attachments list Backport of https://github.com/odoo/odoo/pull/186033 Forward-Port-Of: odoo/odoo#186364
To reproduce: ============= - with service product S with create project & task - create sale order with that product - with another service product E with Re-invoice Expenses at cost - create expense with this product and link it to the first sale order - go back to sale order, we find product E added to sale order - create invoice and post it Problem: ======== on project updates we have the expense + the customer invoice which gives wrong profits in stats Solution: ========= e
Original PR description
To reproduce: ============= - with service product S with create project & task - create sale order with that product - with another service product E with Re-invoice Expenses at cost - create expense with this product and link it to the first sale order - go back to sale order, we find product E added to sale order - create invoice and post it Problem: ======== on project updates we have the expense + the customer invoice which gives wrong profits in stats Solution: ========= exclude the customer invoice from the revenues when it's linked to an expense, as the expense is already included in the revenues opw-4000095 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186078 Forward-Port-Of: odoo/odoo#182165
Previously, reordering the child menu of a newly added menu item didn't reflect immediately in the UI, and was only shown once saved. This fix ensures that new menu and its child items are updated correctly after reordering, both visually and functionally, without requiring a save action. The `addMenu` function now adds new menu item to the state before updating the internal map. The internal map is then updated with a reference to the state.This ensures that changes to the menu are immedi
Original PR description
Previously, reordering the child menu of a newly added menu item didn't reflect immediately in the UI, and was only shown once saved. This fix ensures that new menu and its child items are updated correctly after reordering, both visually and functionally, without requiring a save action. The `addMenu` function now adds new menu item to the state before updating the internal map. The internal map is then updated with a reference to the state.This ensures that changes to the menu are immediately reflected in the UI, as the internal map have reference to the updated state. task-3969045 Forward-Port-Of: odoo/odoo#180180
After this commit 784f1511 , The `float_round()` functionality is changed. Before this commit, If the `qty_available` is 0.57: ``` In [2]: float_round(0.57,2) Out[2]: 0.5700000000000001 After this commit: In [2]: float_round(0.57,2) Out[2]: 0.57 ``` Now, while executing this line of code https://github.com/odoo/odoo/blob/baea953d248471e8aef60e02c1216f77941f1951/addons/mrp/models/product.py#L244 ``` Before: In [3]: 0.5700000000000001*100//1 Out[3]: 57.0 After: In [3]: 0.57*
Original PR description
After this commit 784f1511 , The `float_round()` functionality is changed. Before this commit, If the `qty_available` is 0.57: ``` In [2]: float_round(0.57,2) Out[2]: 0.5700000000000001 After this…
After this commit 784f1511 , The `float_round()` functionality is changed. Before this commit, If the `qty_available` is 0.57: ``` In [2]: float_round(0.57,2) Out[2]: 0.5700000000000001 After this commit: In [2]: float_round(0.57,2) Out[2]: 0.57 ``` Now, while executing this line of code https://github.com/odoo/odoo/blob/baea953d248471e8aef60e02c1216f77941f1951/addons/mrp/models/product.py#L244 ``` Before: In [3]: 0.5700000000000001*100//1 Out[3]: 57.0 After: In [3]: 0.57*100//1 Out[3]: 56.0 ``` These differences leads to blocking the upgrade process. ``` Traceback (most recent call last): File "/tmp/tmpft9eq3rf/migrations/testing.py", line 212, in test_check self.check(value) File "/tmp/tmpft9eq3rf/migrations/stock/tests/test_on_hand_quantity.py", line 90, in check self.assertEqual(before_results, self.convert_check(after_results), self.message) AssertionError: Lists differ: [[12,[7979 chars]6, '57'], [20249, '17.06'], [20250, '1705'], [[12354 chars]'1']] != [[12,[7979 chars]6, '56'], [20249, '17.06'], [20250, '1705'], [[12354 chars]'1']] First differing element 529: [20246, '57'] [20246, '56'] ``` upg-2096343 opw-4224012 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#183289
Issue Summary: During the upgrade from Odoo version 16.0 to 17.0, a discrepancy has emerged in the product configuration, specifically with the "Buy" route. The problem arises when computing the available quantity using the _compute_quantities_dict function. see: https://github.com/odoo/odoo/commit/6d8f184f09c213be068f911dd327ffe84fde8bab Problem Description: In version 17.0, when fetching the domain_Quant using the _get_domain_locations function, the domain returned is ('location
Original PR description
Issue Summary: During the upgrade from Odoo version 16.0 to 17.0, a discrepancy has emerged in the product configuration, specifically with the "Buy" route. The problem arises when computing the…
Issue Summary:
During the upgrade from Odoo version 16.0 to 17.0, a discrepancy has emerged in the product configuration, specifically with the "Buy" route.
The problem arises when computing the available quantity using the _compute_quantities_dict function.
see:
https://github.com/odoo/odoo/commit/6d8f184f09c213be068f911dd327ffe84fde8bab
Problem Description:
In version 17.0, when fetching the domain_Quant using the _get_domain_locations function, the domain returned is ('location_id', 'any', [(0, '=', 1)])
if no locations are found.
In version 16.0, it returns an empty list [] if no locations are found. This change results in the domain_quant in version 17.0 being
[('product_id', 'in', [2684, 5474, 5475, 5478, 5487, 5522]), ('location_id', 'any', [(0, '=', 1)])],
which leads to {} values, whereas in version 16.0, the domain
would be [('product_id', 'in', [2684, 5474, 5475, 5478, 5487, 5522])], which returns actual values.
Impact:
The inconsistency in the domain operation between versions results in incorrect or missing quantity data after the upgrade, affecting the accuracy of product availability.
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#175116__Current behavior before commit:__ Events with products that use a pricelist with `discount_policy` set `without_discount` cause 403 for public users on event pages if website setting `show_line_subtotals_tax_selection` = `tax_included`. __Reason:__ This is because of access right issues on taxes for `price_incl` being displayed on the event page. __Fix:__ Added `compute_sudo=True` to the field `price_incl`. __Steps:__ 1. Create new product `detailed_type` `event` with a high pri
Original PR description
__Current behavior before commit:__ Events with products that use a pricelist with `discount_policy` set `without_discount` cause 403 for public users on event pages if website setting…
__Current behavior before commit:__ Events with products that use a pricelist with `discount_policy` set `without_discount` cause 403 for public users on event pages if website setting `show_line_subtotals_tax_selection` = `tax_included`. __Reason:__ This is because of access right issues on taxes for `price_incl` being displayed on the event page. __Fix:__ Added `compute_sudo=True` to the field `price_incl`. __Steps:__ 1. Create new product `detailed_type` `event` with a high price Ex:100. 2. Set the website pricelist entry for this price as lower price Ex:50. 3. Change pricelist `discount_policy` to `without_discount`. 4. Change website setting: (Display Product Price) to (Tax Included) 4. Create event with custom product. 5. Publish event and view the event page from a public user. opw-4264353 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#184893
Monaco is sharing the same CoA as France, therefore we should use l10n_fr when installing account with a company from Monaco. opw-4197369 Forward-Port-Of: odoo/odoo#181587 Forward-Port-Of: odoo/odoo#181333
Original PR description
Monaco is sharing the same CoA as France, therefore we should use l10n_fr when installing account with a company from Monaco. opw-4197369 Forward-Port-Of: odoo/odoo#181587 Forward-Port-Of: odoo/odoo#181333
…Exempt tax for sale and purchase Description of the issue/feature this PR addresses: The current GST/HST report tax report (Canada) have a missing lines for 90 and 91 as per the Canada Revenue agency Instructions of tax report Added Exempt tax which is 0% in the Exempt category: More info found at: https://www.canada.ca/en/revenue-agency/services/forms-publications/publications/rc4022/general-information-gst-hst-registrants.html#H1_106 More details for lines 90, 91, and 101: https:
Original PR description
…Exempt tax for sale and purchase Description of the issue/feature this PR addresses: The current GST/HST report tax report (Canada) have a missing lines for 90 and 91 as per the Canada Revenue…
…Exempt tax for sale and purchase Description of the issue/feature this PR addresses: The current GST/HST report tax report (Canada) have a missing lines for 90 and 91 as per the Canada Revenue agency Instructions of tax report Added Exempt tax which is 0% in the Exempt category: More info found at: https://www.canada.ca/en/revenue-agency/services/forms-publications/publications/rc4022/general-information-gst-hst-registrants.html#H1_106 More details for lines 90, 91, and 101: https://www.canada.ca/en/revenue-agency/services/tax/businesses/topics/gst-hst-businesses/complete-file-instructions.html#lines909102 Current behavior before PR: Current Tax report missing line 90 and 91: Desired behavior after PR is merged: The tax report should have lines 90 and 91 and line 101 computed based on lines 90 and 91. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186257 Forward-Port-Of: odoo/odoo#184597
Ease adding voice metadata through message_post. Task- Forward-Port-Of: odoo/odoo#186244
Original PR description
Ease adding voice metadata through message_post. Task- Forward-Port-Of: odoo/odoo#186244
Description of the issue/feature this PR addresses: Described in #184497 Current behavior before PR: Error when selecting a template that contains field you don't have access to Desired behavior after PR is merged: No error occurs --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#184943
Original PR description
Description of the issue/feature this PR addresses: Described in #184497 Current behavior before PR: Error when selecting a template that contains field you don't have access to Desired behavior after PR is merged: No error occurs --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#184943
During `test_drag_and_drop_event_in_calendar`, an error occurs due to the target not being found in drag and drop steps. When the test is performed on the same week as the event, there is a likely chance for the drag and drop steps to be triggered before the rendering of the Monthly Calendar view. When we are changing from weekly to monthly view, we will wait for the latter to be rendered before calling the next steps. runbot-error-105708 runbot-error-105709 Forward-Port-Of: odoo/odoo#18
Original PR description
During `test_drag_and_drop_event_in_calendar`, an error occurs due to the target not being found in drag and drop steps. When the test is performed on the same week as the event, there is a likely chance for the drag and drop steps to be triggered before the rendering of the Monthly Calendar view. When we are changing from weekly to monthly view, we will wait for the latter to be rendered before calling the next steps. runbot-error-105708 runbot-error-105709 Forward-Port-Of: odoo/odoo#186142
Steps to reproduce: - Install Project and sale_timesheet and Accounting - Settings > Enable 'Analytic Accounting' - Create a service product generating a project and task - New Product > Set 'Re-invoice Expenses' to 'Cost' - (If you have hr_expense you need to tick 'Can be expensed') - Create a new quotation for your project generating product > Confirm - Accounting > Vendors > Bills > New > Add your expense product - Set the analytic distribution to your project's (S000... - Customer)
Original PR description
Steps to reproduce: - Install Project and sale_timesheet and Accounting - Settings > Enable 'Analytic Accounting' - Create a service product generating a project and task - New Product > Set…
Steps to reproduce: - Install Project and sale_timesheet and Accounting - Settings > Enable 'Analytic Accounting' - Create a service product generating a project and task - New Product > Set 'Re-invoice Expenses' to 'Cost' - (If you have hr_expense you need to tick 'Can be expensed') - Create a new quotation for your project generating product > Confirm - Accounting > Vendors > Bills > New > Add your expense product - Set the analytic distribution to your project's (S000... - Customer) - Fill in Vendor, Bill Date and Price with arbritrary values > Confirm - Project > ':' Menu on your project's card > Project Updates The analytic line created on vendor bill confirmation is also linked to the sale order line created by the re-invoiced product on the original SO. This error notably does not occur without the sale_timesheet module, and the same flow with hr_expense instead of a vendor bill works flawlessly. Project Updates shows the expense twice under Costs because unlike with the hr_expense module, no expense_id is linked to the account_move_line (Since regular vendor bills do no handle that field). This means we fail to filter the analytic_line in `_get_profitability_aal_domain`, thus reading the same update analytic line and deducting the amount twice. Given that the vendor bill was meant to be treated as an expense, and that the same flow using hr_expense instead of a vendor bill results in only 1 line of costs, we want to replicate that behavior here, but we don't have a clean way to filter for these types of analytic lines. As a workaround we use the property of `_get_costs_items_from_purchase` to label updates in the 'other_purchase_costs' category to single out vendor bill updates and skip processing them the second time they come up. opw-4042729 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180589
Steps to reproduce: - Project app > New Project > New Task - On Task > Subtask tab > Add subtask > Save - On Subtask > Timesheets tab > Record a timesheet - On task > Print timesheets The report shows a line for Task with no timesheets in saas-17.2 and saas-17.4, while it is completely blank in 18.0 (Due to an extra condition added in https://github.com/odoo/odoo/pull/178397). We'd expect only tasks with recorded timesheets to be on the report, regardless of whether their parent tasks
Original PR description
Steps to reproduce: - Project app > New Project > New Task - On Task > Subtask tab > Add subtask > Save - On Subtask > Timesheets tab > Record a timesheet - On task > Print timesheets The report shows a line for Task with no timesheets in saas-17.2 and saas-17.4, while it is completely blank in 18.0 (Due to an extra condition added in https://github.com/odoo/odoo/pull/178397). We'd expect only tasks with recorded timesheets to be on the report, regardless of whether their parent tasks are there or not. Additionally, since subtasks can now appear without parent, the titles have been updated to make tarcking subtask origin easier. opw-4292481 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#185946
This error occurs when we are creating a new operation type in transfer. Steps to reproduce: --- - Install ``l10n_it_stock_ddt`` module - Switch company to ``IT Company`` - Go to transfer and create any new operation type Traceback: --- ``KeyError: 'code'`` At [1], we are facing this error because we are attempting to retrieve ``code`` from the ``vals``, but when we create a new operation type, we only receive ``name`` in the ``vals``. [1]- https://github.com/odoo/odoo/blob/248
Original PR description
This error occurs when we are creating a new operation type in transfer. Steps to reproduce: --- - Install ``l10n_it_stock_ddt`` module - Switch company to ``IT Company`` - Go to transfer and create any new operation type Traceback: --- ``KeyError: 'code'`` At [1], we are facing this error because we are attempting to retrieve ``code`` from the ``vals``, but when we create a new operation type, we only receive ``name`` in the ``vals``. [1]- https://github.com/odoo/odoo/blob/2489a4c4a5aae829bb7dafe24d93529767ce07db/addons/l10n_it_stock_ddt/models/stock_picking.py#L76 sentry-6037671568 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186127
Steps to reproduce: - Install Project and sale_timesheet - Create a project with Timesheet option enabled - Go to that project's setting and allocate hours - Gear Icon > Duplicate The duplicated project has 0 allocated hours, this is odd since sale_timesheet forces that field to copy=False despite every other module allowing it (Even Timesheet). Additionally, copied tasks still have their allocated hours no matter what so it is strange to remove them from the project itself. opw-428495
Original PR description
Steps to reproduce: - Install Project and sale_timesheet - Create a project with Timesheet option enabled - Go to that project's setting and allocate hours - Gear Icon > Duplicate The duplicated project has 0 allocated hours, this is odd since sale_timesheet forces that field to copy=False despite every other module allowing it (Even Timesheet). Additionally, copied tasks still have their allocated hours no matter what so it is strange to remove them from the project itself. opw-4284950 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186292 Forward-Port-Of: odoo/odoo#185890
The problem: In the accounting reports, filter options were not being translated. Steps to reproduce: Install and change to the Danish language. Navigate to Accounting > Reporting > Partner ledger (Kontoudtog) Activate the filter "Only Show Unreconciled Entries" (Vis kun ikke udlignede posteringer) Generate the PDF report. Why it was happening: The array `extra_options` was built dynamically by concatenating raw python strings to it. Those raw strings will not be translated. The f
Original PR description
The problem: In the accounting reports, filter options were not being translated. Steps to reproduce: Install and change to the Danish language. Navigate to Accounting > Reporting > Partner ledger (Kontoudtog) Activate the filter "Only Show Unreconciled Entries" (Vis kun ikke udlignede posteringer) Generate the PDF report. Why it was happening: The array `extra_options` was built dynamically by concatenating raw python strings to it. Those raw strings will not be translated. The fix: Now, we create local variables for each string, using the syntax `<t t-set="label_raw_string">Raw String</t>` which makes the string label_raw_string translatable, then we append it to `extra_options`. opw-4213562 Forward-Port-Of: odoo/enterprise#73301 Forward-Port-Of: odoo/enterprise#72870
Before this commit, if a user didn't remove the prepared orders from the preparation display, all orders would be displayed even after closing and opening a new session. This could cause rendering issues due to the large number of orders. opw-4295258 Forward-Port-Of: odoo/enterprise#73235
Original PR description
Before this commit, if a user didn't remove the prepared orders from the preparation display, all orders would be displayed even after closing and opening a new session. This could cause rendering issues due to the large number of orders. opw-4295258 Forward-Port-Of: odoo/enterprise#73235
Have a node that goes: ```xml <div groups="!module.some_group" /> ``` Before this commit, this case was not handled and that not-group was just ignored. This created confusion as the node, when the user was part of the group, would be invisible, the checkbox invisible would be ticked, and uniticking it had no effect. After this commit, we handle the case, with a second selector in the studio sidebar. opw-4273853 Forward-Port-Of: odoo/enterprise#73233
Original PR description
Have a node that goes: ```xml <div groups="!module.some_group" /> ``` Before this commit, this case was not handled and that not-group was just ignored. This created confusion as the node, when the user was part of the group, would be invisible, the checkbox invisible would be ticked, and uniticking it had no effect. After this commit, we handle the case, with a second selector in the studio sidebar. opw-4273853 Forward-Port-Of: odoo/enterprise#73233
Steps to reproduce ================== - Install account_accountant,web_studio - Go to an invoice - Set the partner's language to French - Print the Invoice without Paiement PDF - Open studio - Edit that report - Add a new text below the invoice header - Save the report and exit studio - Print the same report => Some fields aren't translated Cause of the issue ================== When editing the report, ```xml <strong>Due Date:</strong><br/> ``` is converted to ```xml
Original PR description
Steps to reproduce ================== - Install account_accountant,web_studio - Go to an invoice - Set the partner's language to French - Print the Invoice without Paiement PDF - Open studio - Edit that report - Add a new text below the invoice header - Save the report and exit studio - Print the same report => Some fields aren't translated Cause of the issue ================== When editing the report, ```xml <strong>Due Date:</strong><br/> ``` is converted to ```xml <strong>Due Date:</strong> <br/> ``` This no longer matches the translation key. opw-3730267 Forward-Port-Of: odoo/enterprise#73177 Forward-Port-Of: odoo/enterprise#72393
Steps to reproduce: - New product > Storable; Recurring; Edit 'On Hand Quantity' to 10 - New subscription > Add your product > Confirm - Create Invoice > Confirm > Back to sub - View forecast on order line > 1 reserved; 1 forecasted for next period (This is correct, the subscription is ongoing) - Renew > Confirm > View forecast - 1 reserved for original sub (OK); 2 forecasted for next period This is wrong because renewed subscriptions should no longer have recurring invoices, meaning th
Original PR description
Steps to reproduce: - New product > Storable; Recurring; Edit 'On Hand Quantity' to 10 - New subscription > Add your product > Confirm - Create Invoice > Confirm > Back to sub - View forecast on order line > 1 reserved; 1 forecasted for next period (This is correct, the subscription is ongoing) - Renew > Confirm > View forecast - 1 reserved for original sub (OK); 2 forecasted for next period This is wrong because renewed subscriptions should no longer have recurring invoices, meaning there is no reason to forecast a stock decrease for them. i.e here it should only forecast 1 unit for the next period corresponding to our new subscription (Created by renew). Prior to 17.0 a storable product cannot also be recurring, so this issue is irrelevant there. opw-4239989 Forward-Port-Of: odoo/enterprise#72397
This commit adds voice information to attachments while creating attachments received from meta side. This will let the users play voice messages directly from the discuss channel. Task-3839838 Forward-Port-Of: odoo/enterprise#73291
Original PR description
This commit adds voice information to attachments while creating attachments received from meta side. This will let the users play voice messages directly from the discuss channel. Task-3839838 Forward-Port-Of: odoo/enterprise#73291
Steps to reproduce: 1. select a document 2. open chatter 3. drag(preview part) and drop to the others folder 4. the mail-chatter-dropzone remains open Technical Reason: Removing the unnecessary stop propagation on the search panel's document drop event as it was preventing it from being caught by the window keeping the chatter drop zone open. After this commit: The mail-chatter-dropzone will be closed after being moved to drag documents to the folders. Task-4268738 Forward-Por
Original PR description
Steps to reproduce: 1. select a document 2. open chatter 3. drag(preview part) and drop to the others folder 4. the mail-chatter-dropzone remains open Technical Reason: Removing the unnecessary stop propagation on the search panel's document drop event as it was preventing it from being caught by the window keeping the chatter drop zone open. After this commit: The mail-chatter-dropzone will be closed after being moved to drag documents to the folders. Task-4268738 Forward-Port-Of: odoo/enterprise#72443