Wednesday, April 23, 2025
35 changes · saas-18.2
Enhancements to existing features
Point of Sale product cards now exclude quantities from combo choices when showing item counts. This makes the displayed counts more accurate for staff and helps avoid confusion during checkout.
Original PR description
In this commit: ======= Ensures that combo choice quantities are not included when calculating the product card quantity count. Task: 4676110
Dropdown and autocomplete menus no longer pre-select an item just because the cursor happens to be resting over it when the menu opens. This makes menu behavior more predictable and reduces accidental selections for users.
Original PR description
The mouse cursor automaticaly selects dropdown and autocomplete items if the mouse is on top of the item when the menu opens, this is not expected. After this commit, the mouse cursor only select items if it moves. Task: 4687065 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update changes an internal accounting test so it sets a ranking value directly instead of relying on a delayed background step. This makes the test more predictable and helps reduce false failures without changing product behavior for users.
Original PR description
Increase the field of the rank directly in test instead of going through `_increase_rank` which increases the rank in postcommit. odoo/odoo#205528
Resolved issues and error corrections
Invoice reporting now handles cases where the total quantity is zero when calculating Average Price. This prevents an error in graph or pivot analysis and shows a safe value instead, keeping invoice reporting usable for edge-case invoices.
Original PR description
Currently, an error occurs when the sum of the quantity is zero, and user analyzes invoice data using the `Average Price` measure. **Steps to produce:** - Install the account module. - Navigate to `Invoicing > Customers > Invoices > New`. - Add required fields and set `quantity to zero` and confirm the invoice. - Navigate to `Reporting > Invoice Analysis`, Switch to `Graph or Pivot view` and set measure to Average Price. **Error:** `DivisionByZero: division by zero` **Root Cause:** At [1], the `_read_group_select` method for computing average price, divides the sum of price_subtotal by the sum of quantity. If sum of the quantity is zero, it leads to a division by zero error. [1] https://github.com/odoo/odoo/blob/97c2381aaeb1cca56288a1cca3c8359ea712ab6e/addons/account/report/account_invoice_report.py#L165 This commit ensures that the average price calculation safely returns 0 when the total quantity is zero. Sentry - 6358566076
Miscellaneous changes
## Details: The function get_link_preview_from_html is a common tool used in many modules, one of them documents. When you add a link on a workspace that response with a content with a xml declaration (ex. "<!--?xml version="1.0" encoding="UTF-8"?-->"), this will raise the next ValueError: "Unicode strings with encoding declaration are not supported. Please use bytes input or XML fragments without declaration." At the moment that the string is being parsed as a html element, this str
Original PR description
## Details: The function get_link_preview_from_html is a common tool used in many modules, one of them documents. When you add a link on a workspace that response with a content with a xml…
## Details: The function get_link_preview_from_html is a common tool used in many modules, one of them documents. When you add a link on a workspace that response with a content with a xml declaration (ex. "<!--?xml version="1.0" encoding="UTF-8"?-->"), this will raise the next ValueError: "Unicode strings with encoding declaration are not supported. Please use bytes input or XML fragments without declaration." At the moment that the string is being parsed as a html element, this string has been cleaned, to avoid the issue, we can only remove this xml declaration because this element is only being used to extract information about the page. ## Impacted versions: 18.0 and later ## Steps to reproduce: 1. Go to Documents App 2. Add a link in any workspace with xml declaration (ex. https://www.buffalo.jp/s3/guide/crmm/userguide/99/en/pc_index.html) ## Current behavior: Raise Value Error "Unicode strings with encoding declaration are not supported. Please use bytes input or XML fragments without declaration." ## Expected behavior: Link should be saved. ### Task OPW-4675813 Forward-Port-Of: odoo/odoo#205049
This fixes an issue in the Mail app where removing email recipient tags with the keyboard could trigger an error. Users can now manage recipients in the email composer without interruptions.
Original PR description
[This commit] used `record.id` as if they were `record.resId` resulting in an issue when trying to delete a tag. How to reproduce: - Use the chatter to send an email using the full composer - add some email recipients - try to remove them using backspace -> traceback This fix correctly renames properties that should be `resId`, and removes the `id` override (`record.id` is a value specific to the relational model from `/web/`). [This commit]: https://github.com/odoo/odoo/commit/1f34abc173f07b6d20c08a27ec57c7025cb20562 task-4731774 Co-authored-by: Damien Abeloos <abd@odoo.com> Co-authored-by: Kadam Darji <kmdi@odoo.com>
Receipt lines in Point of Sale now display with more consistent spacing when they include notes or lot/serial numbers. This removes an awkward margin and helps printed receipts look cleaner and easier to read.
Original PR description
- Remove weird margin on receipt for order lines that have a note or a lot/serial number - Adjust gap to align with rest task-id: 4680438 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue where UAE invoice documents could show the word "Invoice" twice when printed, previewed, or emailed. UAE companies now see the correct "Tax Invoice" title, making customer-facing documents clearer and more professional.
Original PR description
In a previous commit 1accf51091229811a0b0c1d2356a56e5f7fde44c, we were concatenating the invoice title instead of replacing it. This caused the word "Invoice" to appear twice on printed, previewed, or emailed invoice documents when using the UAE localization. This commit correctly replaces the title using XPath. For companies based in the UAE, the title now shows as "Tax Invoice" without duplication. OPW-4722229 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users who only have access to settings can now open the settings page without encountering an error. The change safely retrieves the default journal in the background, improving reliability for administrative workflows.
Original PR description
When opening settings as a user with only access to settings results in a crash because the user does not have access to 'Journal'. Covered by `test_settings_access` in base when installing "test_full_discuss". The solution is simply to query for the default journal using sudo.
The attendance planning Gantt view now shows only one day, week, or month at a time, depending on the selected scale. This keeps the view focused and prevents users from seeing an overly broad or confusing date range.
Original PR description
In this PR we modify the gantt_model to only display 1 day/week/month at a time
The restaurant preparation display tests now wait for order synchronization before moving to the next step. This prevents automated checks from running too quickly and failing before the server has finished responding, improving release validation reliability.
Original PR description
Since we didn't wait for synchronization when clicking on the order button, tours are too fast and the response from the server isn't received in time. This commit adds a wait to ensure that the synchronization is complete before proceeding with the next step. Runbot: 181579
After clearing the cache you can have inconsistent reward lines that have no coupon associated with them. Steps to reproduce: ------------------- * Create an order and add any reward (Buy X Get Y for example) * Go to the backend to make sure the order is saved in the database * Go back to the POS and clear the cache > Observation: You are stuck on the loading screen Why the fix: ------------ To avoid having inconsistent reward lines that have no coupon associated with them, we delet
Original PR description
After clearing the cache you can have inconsistent reward lines that have no coupon associated with them. Steps to reproduce: ------------------- * Create an order and add any reward (Buy X Get Y for example) * Go to the backend to make sure the order is saved in the database * Go back to the POS and clear the cache > Observation: You are stuck on the loading screen Why the fix: ------------ To avoid having inconsistent reward lines that have no coupon associated with them, we delete all the lines of an order that contains wrong data. As this is not supposed to happen (clearing the cache is a debug functionality), we can safely delete the lines because it's wont impact the real workflow of the users. opw-4655422 Forward-Port-Of: odoo/odoo#206549 Forward-Port-Of: odoo/odoo#202752
Description: Adding a warning message when checking the option to enable the audit trail as this option can't be disabled if there are any existing move lines. opw-4596812 opw-4346608 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#200072
Original PR description
Description: Adding a warning message when checking the option to enable the audit trail as this option can't be disabled if there are any existing move lines. opw-4596812 opw-4346608 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#200072
is_freelancer is not passed, but freelancer is as value to the XML opw-4634677 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#206127
Original PR description
is_freelancer is not passed, but freelancer is as value to the XML opw-4634677 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#206127
In commit aca36072a8adcdc2263f5dcc12a3c9fb374a025e a new data file was created but not included in the manifest. So it is never loaded. This commit removes the file (since it is not used anyway). task: None Forward-Port-Of: odoo/odoo#206612
Original PR description
In commit aca36072a8adcdc2263f5dcc12a3c9fb374a025e a new data file was created but not included in the manifest. So it is never loaded. This commit removes the file (since it is not used anyway). task: None Forward-Port-Of: odoo/odoo#206612
overtime_status is currently readonly which prevents record importation of extra hours, since if they are not approved, the compute will get triggered Forward-Port-Of: odoo/odoo#206719 Forward-Port-Of: odoo/odoo#206589
Original PR description
overtime_status is currently readonly which prevents record importation of extra hours, since if they are not approved, the compute will get triggered Forward-Port-Of: odoo/odoo#206719 Forward-Port-Of: odoo/odoo#206589
Related enterprise PR : https://github.com/odoo/enterprise/pull/81754 Forward-Port-Of: odoo/odoo#206694 Forward-Port-Of: odoo/odoo#205379
Original PR description
Related enterprise PR : https://github.com/odoo/enterprise/pull/81754 Forward-Port-Of: odoo/odoo#206694 Forward-Port-Of: odoo/odoo#205379
Steps to reproduce the issue: - Add a popup with a 0.0001 days config. - Visit the page as a non-connected user. - The popup opens at some point. - Close the popup. - Wait 10 seconds. - Refresh the page ---> The popup never reappears. This issue comes from the fact that we were setting a non-integer value for the cookie expiration. The "max-age" attribute does not accept float values, so the cookie is treated as a "session" cookie. It only expires when the session ends, which can be e
Original PR description
Steps to reproduce the issue: - Add a popup with a 0.0001 days config. - Visit the page as a non-connected user. - The popup opens at some point. - Close the popup. - Wait 10 seconds. - Refresh the…
Steps to reproduce the issue: - Add a popup with a 0.0001 days config. - Visit the page as a non-connected user. - The popup opens at some point. - Close the popup. - Wait 10 seconds. - Refresh the page ---> The popup never reappears. This issue comes from the fact that we were setting a non-integer value for the cookie expiration. The "max-age" attribute does not accept float values, so the cookie is treated as a "session" cookie. It only expires when the session ends, which can be effectively "never" on some browsers that keep sessions open indefinitely. This used to work before commit [1] because we were also setting an "expires" attribute. When the "max-age" attribute was invalid, the browser would fallback to the "expires" attribute. Since that commit removed the "expires" attribute, the only remaining value (max-age) is invalid, and the popup never reappears as expected. This fix ensures the value used in "max-age" is always an integer, avoiding any invalid cookie behavior. [1]: https://github.com/odoo/odoo/commit/006ee1fc470eabdcbde68077259cf543633d6490 task-4690318 Forward-Port-Of: odoo/odoo#206429
This is a backport of commit 9b86deb to saas-18.1. Before this commit, the following errors would occur during start-up: - `systemd-timesyncd` would fail to start - Several errors related to locale settings The `systemd-timesyncd` problem was actually caused by it trying to start too early. By disabling the autostart of the service, it is instead started as a dependency of `systemd-timedate`. This allows it to start without errors. The locale errors were caused by the default locale b
Original PR description
This is a backport of commit 9b86deb to saas-18.1. Before this commit, the following errors would occur during start-up: - `systemd-timesyncd` would fail to start - Several errors related to locale settings The `systemd-timesyncd` problem was actually caused by it trying to start too early. By disabling the autostart of the service, it is instead started as a dependency of `systemd-timedate`. This allows it to start without errors. The locale errors were caused by the default locale being set to `en_GB` even though only `en_US` was setup during the build process. By setting the `/etc/default/locale` file to `en_US` and removing all the evironment variables, the errors are fixed. We also unset all language environment variables during the image build process, preventing the same locale errors from appearing. task-4687121 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206015
Before this commit, when Chromium was running in kiosk mode under Wayland, it would not detect that the input device was a touchscreen. This resulted in touchscreen-specific code (such as hiding the cursor in the self-order kiosk) not working. After this commit, we pass the `--touch-events` flag to Chromium when running in kiosk mode, which forces touch events to be enabled. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odo
Original PR description
Before this commit, when Chromium was running in kiosk mode under Wayland, it would not detect that the input device was a touchscreen. This resulted in touchscreen-specific code (such as hiding the cursor in the self-order kiosk) not working. After this commit, we pass the `--touch-events` flag to Chromium when running in kiosk mode, which forces touch events to be enabled. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206025
Commit ebb09234e6444576e7e934f53de1d23a0d9760d2 made it so that bank account are archived instead of deleted meaning that they are never deleted in the DB. If a user tries to create a new bank account for the same partner with the same account number, the following validation error is raised: "The operation cannot be completed: The combination Account Number/Partner must be unique." This commit introduces a new UserError when a user attempts to create an account that was previously arch
Original PR description
Commit ebb09234e6444576e7e934f53de1d23a0d9760d2 made it so that bank account are archived instead of deleted meaning that they are never deleted in the DB. If a user tries to create a new bank account for the same partner with the same account number, the following validation error is raised: "The operation cannot be completed: The combination Account Number/Partner must be unique." This commit introduces a new UserError when a user attempts to create an account that was previously archived. It also updates the message in the chatter from "deleted" to "archived." opw-4669340 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206180 Forward-Port-Of: odoo/odoo#203474
Description of the issue/feature this PR addresses: Kanban view of the website pages not working (opw-4651572) Current behavior before PR: The kanban view was not working if the database only contains one website because of the group multi-website not set on the users so the t-if="record.website_id.value" cannot be evaluated. Desired behavior after PR is merged: The group attribute is now set correctly on the parent div so the if statement is working properly --- I confirm I
Original PR description
Description of the issue/feature this PR addresses: Kanban view of the website pages not working (opw-4651572) Current behavior before PR: The kanban view was not working if the database only contains one website because of the group multi-website not set on the users so the t-if="record.website_id.value" cannot be evaluated. Desired behavior after PR is merged: The group attribute is now set correctly on the parent div so the if statement is working properly --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#203693
<b>Steps to produce:</b> 1) Install CRM 2) In debug mode, open the stages from the crm configuration 3) Give a long text to Requirements with spaces to the stage 'new' 4) Now open my pipeline and hover on the new stage <b>Issue:-</b> When the user gives a long text with spaces to the requirements in the first stage, It is overflowing the screen. <b>Solution:-</b> Add the class text-prewrap to the tooltip of the kanban header. So the "formatted text" is respected for the k
Original PR description
<b>Steps to produce:</b> 1) Install CRM 2) In debug mode, open the stages from the crm configuration 3) Give a long text to Requirements with spaces to the stage 'new' 4) Now open my pipeline and hover on the new stage <b>Issue:-</b> When the user gives a long text with spaces to the requirements in the first stage, It is overflowing the screen. <b>Solution:-</b> Add the class text-prewrap to the tooltip of the kanban header. So the "formatted text" is respected for the kanban stage. opw-4623639 Forward-Port-Of: odoo/odoo#206193
The issue was introduced by: https://github.com/odoo/odoo/commit/90158f647ba610b31499555641c9db8450b49c4c The issue has been fixed by: https://github.com/odoo/odoo/commit/b1666c61bbc9d7e7b920483e168c6048ecde011c This commit is adding a test for it. **Steps to reproduce:** - Install Accounting and purchase_stock - Activate a foreign currency (e.g. Euro) - Create a PO: * Vendor: [any] * Currency: EUR * Product: [any with a Unit Price and a tax] * Payment Terms: [any] (e.g
Original PR description
The issue was introduced by: https://github.com/odoo/odoo/commit/90158f647ba610b31499555641c9db8450b49c4c The issue has been fixed by:…
The issue was introduced by: https://github.com/odoo/odoo/commit/90158f647ba610b31499555641c9db8450b49c4c The issue has been fixed by: https://github.com/odoo/odoo/commit/b1666c61bbc9d7e7b920483e168c6048ecde011c This commit is adding a test for it. **Steps to reproduce:** - Install Accounting and purchase_stock - Activate a foreign currency (e.g. Euro) - Create a PO: * Vendor: [any] * Currency: EUR * Product: [any with a Unit Price and a tax] * Payment Terms: [any] (e.g. 15 Days) - Confirm the PO - Validate the receipt order - Go to "Accounting / Vendors / Bills" - Create a new bill - In "Auto-Complete" field, select the created PO **Issue:** A traceback is raised due to a division by zero. **Cause:** The bill and its lines are created from some information coming from the PO. In the computation of the needed terms of the bill, a computation of the taxes is called on the lines (i.e. _compute_all_tax). During that computation, the rate is computed as followed: (*) rate = line.amount_currency / line.balance if line.balance else line.currency_rate and later, rate is used as followed: 'balance': tax['amount'] / rate When "purchase_stock" module is not installed, there is no issue because "_prepare_account_move_line" method from "purchase.order. line" model doesn't initialized "amount_currency" nor "balance". Therefore, the result of (*) falls back on "line.currency_rate" which is not zero. However, when "purchase_stock" module is installed, "balance" is initialized in "_prepare_account_move_line" but not "amount_currency", leading a result of 0 for (*). opw-4681735 Forward-Port-Of: odoo/odoo#205233
This commit targets to add the necessary demo data for testing Mexican payroll localization target: saas-17.4 -> master task-4486643 Linked PR: [odoo/enterprise#80451](https://github.com/odoo/enterprise/pull/80451) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#199888
Original PR description
This commit targets to add the necessary demo data for testing Mexican payroll localization target: saas-17.4 -> master task-4486643 Linked PR: [odoo/enterprise#80451](https://github.com/odoo/enterprise/pull/80451) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#199888
`odoo_origin` and `odoo_dev` aliases used to reset odoo code on a dev/origin branch were sometimes returning an error not finding the fetched branch. They are now resetting on FETCH_HEAD to ensure the reset on the latest fetched branch. Forward-Port-Of: odoo/odoo#206823
Original PR description
`odoo_origin` and `odoo_dev` aliases used to reset odoo code on a dev/origin branch were sometimes returning an error not finding the fetched branch. They are now resetting on FETCH_HEAD to ensure the reset on the latest fetched branch. Forward-Port-Of: odoo/odoo#206823
The test introduced in 5734ba9 opens the product catalog, filters it, then adds a product and updates its quantity. The problem is that when the product is already visible in the catalog (before filtering), the next steps can be triggerred while the filtering is still being processed. Once the filtering is done, the state of the product in the catalog is "reverted" to how it was when the filtering was called. This might be inconsistent with the state expected by the step the tour is currently in
Original PR description
The test introduced in 5734ba9 opens the product catalog, filters it, then adds a product and updates its quantity. The problem is that when the product is already visible in the catalog (before filtering), the next steps can be triggerred while the filtering is still being processed. Once the filtering is done, the state of the product in the catalog is "reverted" to how it was when the filtering was called. This might be inconsistent with the state expected by the step the tour is currently in. We can solve this by adding a different product to be filtered out. This allows to add a blocking step that just waits for the catalog not to include the new product. Fixes runbot errors: [162099](https://runbot.odoo.com/odoo/error/162099) [163417](https://runbot.odoo.com/odoo/error/163417) Forward-Port-Of: odoo/odoo#206219
The UAN, PAN and ESIC number fields on the IN employee have a unique constraint. However, they are not set to not being copied upon record duplication, which would cause duplication impossible. This PR fixes the issue by not copying the value of those field upon duplication. task-4708324 Forward-Port-Of: odoo/enterprise#83029
Original PR description
The UAN, PAN and ESIC number fields on the IN employee have a unique constraint. However, they are not set to not being copied upon record duplication, which would cause duplication impossible. This PR fixes the issue by not copying the value of those field upon duplication. task-4708324 Forward-Port-Of: odoo/enterprise#83029
Most tests of the module need to create a sale order, which requires the `group_sale_salesman` at least. Set this group. https://runbot.odoo.com/odoo/error/163649 Forward-Port-Of: odoo/enterprise#83802
Original PR description
Most tests of the module need to create a sale order, which requires the `group_sale_salesman` at least. Set this group. https://runbot.odoo.com/odoo/error/163649 Forward-Port-Of: odoo/enterprise#83802
Fix certificate generation for AR companies when other LATAM countries are installed. opw-4584457 Forward-Port-Of: odoo/enterprise#82527
Original PR description
Fix certificate generation for AR companies when other LATAM countries are installed. opw-4584457 Forward-Port-Of: odoo/enterprise#82527
In this PR we : -Allow manual input of source tax adjustments -Improve transmission error messages -Add missing translations -Reintroduce work information and skills tab Forward-Port-Of: odoo/enterprise#83730 Forward-Port-Of: odoo/enterprise#81754
Original PR description
In this PR we : -Allow manual input of source tax adjustments -Improve transmission error messages -Add missing translations -Reintroduce work information and skills tab Forward-Port-Of: odoo/enterprise#83730 Forward-Port-Of: odoo/enterprise#81754
### Steps to reproduce: - Create a task in Field Service - Navigate to the product's catalog through the smart button - Add some products to the SO - Filter with 'Added products' - Notice the quantity bar is not shown ### Cause: This is happening as when click on the product smart button we are passing the order_id in the context to get the order lines info https://github.com/odoo/enterprise/blob/6e7525e0e0c2858e028694e9227077b2275d88c5/industry_fsm_sale/static/src/components/pr
Original PR description
### Steps to reproduce: - Create a task in Field Service - Navigate to the product's catalog through the smart button - Add some products to the SO - Filter with 'Added products' - Notice the quantity bar is not shown ### Cause: This is happening as when click on the product smart button we are passing the order_id in the context to get the order lines info https://github.com/odoo/enterprise/blob/6e7525e0e0c2858e028694e9227077b2275d88c5/industry_fsm_sale/static/src/components/product_catalog/kanban_model.js#L21-L26 but if we still didn't create an order for this task order_id will be false, so it won't have an order to fetch its data and will just add the default data where the quantity will be 0 https://github.com/odoo/enterprise/blob/6e7525e0e0c2858e028694e9227077b2275d88c5/industry_fsm_sale/models/sale_order.py#L45-L48 ### Fix: If we have a fsm_task we can fallback on its order_id if order_id is false. opw-4712922 Forward-Port-Of: odoo/enterprise#83396
Currently, a traceback occurs when the user clicks critical path in tasks gantt. To reproduce this issue: 1) Install Project and add the `Use Task Dependencies` group to the current user 2) Open the list view of the project 3) Enable the `Task Dependencies` to any one project 4) Now remove all the start dates from the Planned Date for all tasks 5) Open the Gantt view of the tasks and add a task 6) Refresh the page, and click the `Get Critical Path` button Error:- ``` KeyErro
Original PR description
Currently, a traceback occurs when the user clicks critical path in tasks gantt. To reproduce this issue: 1) Install Project and add the `Use Task Dependencies` group to the current user 2) Open the…
Currently, a traceback occurs when the user clicks critical path in tasks gantt. To reproduce this issue: 1) Install Project and add the `Use Task Dependencies` group to the current user 2) Open the list view of the project 3) Enable the `Task Dependencies` to any one project 4) Now remove all the start dates from the Planned Date for all tasks 5) Open the Gantt view of the tasks and add a task 6) Refresh the page, and click the `Get Critical Path` button Error:- ``` KeyError: 24 ``` https://github.com/odoo/enterprise/blob/c9a753fce85dfb09dc413831993e63c7736d258a/project_enterprise/models/project_task.py#L1544 From the above line, the traceback is occurring because the `path_last_task` will take the value from the sorted_tasks's first record. But we don't have any `planned_date_begin` in any task except the one we added in the Gantt view. So the first task which is `path_last_task` will not execute further because of this, https://github.com/odoo/enterprise/blob/c9a753fce85dfb09dc413831993e63c7736d258a/project_enterprise/models/project_task.py#L1529-L1531 This leads to the above traceback when we compare the value of the `path_last_task` from the `total_time` with the current task. https://github.com/odoo/enterprise/blob/c9a753fce85dfb09dc413831993e63c7736d258a/project_enterprise/models/project_task.py#L1544 We can resolve this issue by taking the `path_last_task` if only the task contains `planned_date_begin`. sentry-6327461743 Forward-Port-Of: odoo/enterprise#80195
This error shows up in 18.2, possibly because by waiting more for browser responses #206271 made it more likely that this error would have the time to be sent back down the pipe (also might be a change in chatter impl which makes 18.2 more sensible). However it's likely a global issue: when the tour "click[s] on ticket", it does a full page navigation then triggers the async load of a chatter which can take a pretty long while. It seems like one of the tour teardown steps can cause the loadin
Original PR description
This error shows up in 18.2, possibly because by waiting more for browser responses #206271 made it more likely that this error would have the time to be sent back down the pipe (also might be a change in chatter impl which makes 18.2 more sensible). However it's likely a global issue: when the tour "click[s] on ticket", it does a full page navigation then triggers the async load of a chatter which can take a pretty long while. It seems like one of the tour teardown steps can cause the loading of the chatter bundle to get cancelled, which is then raised as an exception. The error is triggered from `getBundle` while reading the response body, but it just wraps and forwards the error it gets, and swallowing all bundle errors is probably a bad idea... https://runbot.odoo.com/odoo/error/134748 Forward-Port-Of: odoo/enterprise#83871
This commit modifies Elvera and Roque demo data for hr mexican localization target: 17.0 -> master task-4486643 Forward-Port-Of: odoo/enterprise#80451 Forward-Port-Of: odoo/enterprise#78048
Original PR description
This commit modifies Elvera and Roque demo data for hr mexican localization target: 17.0 -> master task-4486643 Forward-Port-Of: odoo/enterprise#80451 Forward-Port-Of: odoo/enterprise#78048