Wednesday, February 19, 2025
71 changes · saas-18.2
Enhancements to existing features
The purchase dashboard has been visually refined with improved colors, layout spacing, and button styling. These changes make the dashboard easier to read and more responsive across different screen sizes, improving the day-to-day purchasing experience.
Original PR description
This PR improves the purchase dashboard design (colors & layout). task-4508833 | Before | After | |--------|--------| |  |  | | | ) | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The Indian e-waybill demo setup now turns on the e-waybill feature automatically for the demo company. This makes test and demo environments easier to use for internal teams without extra manual configuration.
Original PR description
Before this commit: When installing `l10n_in_ewaybill` with `-i` while starting the server or installing the module from apps, issue the demo data is loaded but the ewaybill feature is not active After this commit: Ewaybill feature will be activated for demo company because it's quite useful for internal purposes specially for developers, testers to ease out the process 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
Issue: When changing the company logo, if the image contains a white background it will mix with the header's shape color. This is because the shape is displayed on top of the image. Adding a negative z-index ensures the image is over the shape and doesn't mix with it. task-4471578 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#194347
Original PR description
Issue: When changing the company logo, if the image contains a white background it will mix with the header's shape color. This is because the shape is displayed on top of the image. Adding a negative z-index ensures the image is over the shape and doesn't mix with it. task-4471578 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#194347
Search filters and fields can now be hidden or shown using the same user and company context already supported in search domains. This prevents incorrect filter visibility in multi-company or user-specific setups, making search views behave more consistently.
Original PR description
Since [1] it's possible to use the `user.evalContext` and the newly introduced key `companies` on the domain in the searchModel. But it wasn't possible to use the `user.evalContext` on the invisible attribute of the filter and field tags of the searchModel. This PR fixes this issue and allows the use of `user.evalContext` and the newly introduced key `companies` on the invisible attributes of the tags on the searchModel. [1] : https://github.com/odoo/odoo/commit/19b450d4a222ec817eb2af6edab87044428e0d28
This update restores expected behavior for list-based actions in areas such as Accounting, Inventory, and data cleanup after a previously removed internal helper caused compatibility issues. Users should see the same behavior as before when working with selected records, while customizations that extend these screens remain supported.
Original PR description
In this commit: https://github.com/odoo/odoo/commit/1e4e40cf78fe8151dffdcb19df2688787084732c We removed getSelectedResIds, but this function is still needed in some overrides. This commit removes the calls to that function while keeping the same behaviour as before. no-task linked:https://github.com/odoo/enterprise/pull/79589
This update moves OdooBot status test data into the correct Mail testing area instead of keeping it in Web. It prevents automated test failures caused by data being defined in the wrong module, improving reliability for future changes.
Original PR description
Before this commit, the mock server records in the `web` module would contain the `im_status` field for OdooBot. This would cause tests to fail as the field is defined in the `mail` module. This commit fixes the issue by removing the `im_status` field in the `web` module and add the `im_status` for the OdooBot in the `mail` mock server. rb-116442
This update adjusts the Accounting spreadsheet dashboard so it only appears when the full accounting features it relies on are available. It prevents users with basic invoicing access from seeing dashboard content or links that are not relevant or available to them.
Original PR description
Since account_reports is now installed with invoicing, some dependencies need to change. see https://github.com/odoo/enterprise/pull/77895 * spreadsheet_dashboard_account_accountant: had account_reports as a dependency, but since account_reports is now available with just invoicing, it doesn't make sense to display something like a debt to equity ratio. Also the link to the Accounting menu is only available with the `accountant` module.
This fix updates the Point of Sale settlement flow test to better cover customer search and scrolling on mobile devices. It helps ensure staff can reliably find and select customers when settling due amounts in mobile POS workflows.
Original PR description
- Simplify tour `SettleDueAmountMoreCustomers` using `searchCustomerValue(..., true)` (see linked community PR). community PR: https://github.com/odoo/odoo/pull/197357 task-id: 4550203
This change updates several list-view customizations after a shared selection helper was removed. It prevents errors in affected screens while keeping the previous user behavior unchanged.
Original PR description
In this commit: https://github.com/odoo/odoo/commit/1e4e40cf78fe8151dffdcb19df2688787084732c We removed getSelectedResIds, but this function is still needed in some overrides. This commit removes the calls to that function while keeping the same behaviour as before. no-task linked:https://github.com/odoo/odoo/pull/198121
The logic for the generated SQL for x2many fields is incorrect when we have both False and values in `in` conditons for x2many fields. We must do 2 sub-queries in that case. For example, in `[1, False]` means we do not have any records in the comodel or we `1` is linked to the model through the relation. We could do it in one-subquery, group by the model's id and filter using a having condition `COUNT(CASE ...)`, but that would complexity the code for an edge case. The basic case, where we h
Original PR description
The logic for the generated SQL for x2many fields is incorrect when we have both False and values in `in` conditons for x2many fields. We must do 2 sub-queries in that case. For example, in `[1, False]` means we do not have any records in the comodel or we `1` is linked to the model through the relation. We could do it in one-subquery, group by the model's id and filter using a having condition `COUNT(CASE ...)`, but that would complexity the code for an edge case. The basic case, where we have just False in the values, still inverses the existance condition and searches the whole comodel. odoo/enterprise#79593 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197890
Since odoo/odoo#196778, a portal test template has been added. Missing the `primary`attribute in this template affects all the portal templates. This commit adds this attribute to the test template. Steps to reproduce: - Install a module that inherits `portal.mixin` such as sale and `test_mail_full` - Go to a sale order page in the portal - Chatter is at the top of the page Forward-Port-Of: odoo/odoo#198259
Original PR description
Since odoo/odoo#196778, a portal test template has been added. Missing the `primary`attribute in this template affects all the portal templates. This commit adds this attribute to the test template. Steps to reproduce: - Install a module that inherits `portal.mixin` such as sale and `test_mail_full` - Go to a sale order page in the portal - Chatter is at the top of the page Forward-Port-Of: odoo/odoo#198259
In this pr https://github.com/odoo/odoo/commit/0b8bd891fad1c84607fe147a32d705917341fed7 we improved the partner form but by doing that we removed the use of the auto_save_partner widget which was wrong since we need it in the following case: - Create an invoice - Create and edit a new partner - Trying to add a bank account - The account holder was empty since the partner was not saved task-4507042 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/sub
Original PR description
In this pr https://github.com/odoo/odoo/commit/0b8bd891fad1c84607fe147a32d705917341fed7 we improved the partner form but by doing that we removed the use of the auto_save_partner widget which was wrong since we need it in the following case: - Create an invoice - Create and edit a new partner - Trying to add a bank account - The account holder was empty since the partner was not saved task-4507042 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#194870
Refactor the `_run_manufacture` method in the `stock.rule` model to have a separate method to build the domain used to find an existing manufacturing order that can handle the procurement request. Having a separate method provides an easier way to extend the domain in other modules. A similar approach is already used in the `_run_buy` method. Description of the issue/feature this PR addresses: Patching the entire `_run_manufacture` method is required to change the MO domain. Current behav
Original PR description
Refactor the `_run_manufacture` method in the `stock.rule` model to have a separate method to build the domain used to find an existing manufacturing order that can handle the procurement request. Having a separate method provides an easier way to extend the domain in other modules. A similar approach is already used in the `_run_buy` method. Description of the issue/feature this PR addresses: Patching the entire `_run_manufacture` method is required to change the MO domain. Current behavior before PR: The domain is built inside the `_run_manufacture` method Desired behavior after PR is merged: The domain is built in a dedicated method that can be easily overwritten in custom modules. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196396 Forward-Port-Of: odoo/odoo#196156
Versions -------- - 16.0+ Steps ----- 1. Go to Settings / Website; 2. enable the following options: - Comparison Price; - Pricelists: Advanced price rules; - Prevent Sale of Zero Priced Product; 3. create a pricelist setting all prices to 0; 4. make pricelist selectable; 5. set pricelist's Discount Policy to Show public price & discount to customer; 6. go to `/shop`; 7. query the search bar. Issue ----- A strikethrough price is added, despite the item not being a
Original PR description
Versions
--------
- 16.0+
Steps
-----
1. Go to Settings / Website;
2. enable the following options:
- Comparison Price;
- Pricelists: Advanced price rules;
- Prevent Sale of Zero Priced Product;
3. create a pricelist setting all prices to 0;
4. make pricelist selectable;
5. set pricelist's Discount Policy to Show public price & discount to customer;
6. go to `/shop`;
7. query the search bar.
Issue
-----
A strikethrough price is added, despite the item not being available for sale.
Cause
-----
The `_search_render_results_prices` method still checks for `has_discounted_price` and `compare_list_price` after it already knows the product isn't available for sale.
Solution
--------
If `prevent_zero_price_sale` is given for the product, do an early return, disregarding the `has_discounted_price` and `compare_list_price` options.
opw-4263554
Forward-Port-Of: odoo/odoo#197336
Forward-Port-Of: odoo/odoo#195721When the Arabic language was selected, the PoS Restaurant module would error due to date formatting using Arabic numerals. This commit forces Latin digits in the date format to prevent the error. opw-4544010 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196368
Original PR description
When the Arabic language was selected, the PoS Restaurant module would error due to date formatting using Arabic numerals. This commit forces Latin digits in the date format to prevent the error. opw-4544010 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196368
Steps to reproduce: - In website, open the HTML/CSS Editor (Site > HTML/CSS Editor). - In the dropdown, select JS. - Uncomment the given example (about the "Hello World" dialog) and save. - Try to go in edit mode. => Traceback This happens since commit [1], which replaced the dialogs by OWL Dialog ones. Indeed, the call to `super` in the `init` function was forgotten, making the widget not being initialized correctly, and therefore not destroyed correctly either when going in edit mode.
Original PR description
Steps to reproduce: - In website, open the HTML/CSS Editor (Site > HTML/CSS Editor). - In the dropdown, select JS. - Uncomment the given example (about the "Hello World" dialog) and save. - Try to go in edit mode. => Traceback This happens since commit [1], which replaced the dialogs by OWL Dialog ones. Indeed, the call to `super` in the `init` function was forgotten, making the widget not being initialized correctly, and therefore not destroyed correctly either when going in edit mode. This commit adds this missing call. [1]: https://github.com/odoo/odoo/commit/57ed8bc0bf9d1ae2b7542d677a4d7e8fd1899ea2 opw-4243615 Forward-Port-Of: odoo/odoo#183401
Currently a `ParseError` arises when the user installs the `pos_discount` and `pos_sale` modules after deleting the `Service` category in `Invoicing`. Steps to reproduce: --- - Install `Invoicing` application (without demo data) - Invoicing > Configuration > Categories > Delete `Services` - Now install `pos_discount` and `pos_sale` modules Traceback: --- ``` ValueError: External ID not found in the system: product.product_category_services ParseError: while parsing /home/odoo/src
Original PR description
Currently a `ParseError` arises when the user installs the `pos_discount` and `pos_sale` modules after deleting the `Service` category in `Invoicing`. Steps to reproduce: --- - Install `Invoicing`…
Currently a `ParseError` arises when the user installs the `pos_discount` and `pos_sale` modules after deleting the `Service` category in `Invoicing`.
Steps to reproduce:
---
- Install `Invoicing` application (without demo data)
- Invoicing > Configuration > Categories > Delete `Services`
- Now install `pos_discount` and `pos_sale` modules
Traceback:
---
```
ValueError: External ID not found in the system: product.product_category_services
ParseError: while parsing /home/odoo/src/odoo/saas-18.1/addons/pos_discount/data/pos_discount_data.xml:4, somewhere inside <record id="product_product_consumable" model="product.product">
<field name="name">Discount</field>
<field name="available_in_pos">False</field>
<field name="standard_price">0.00</field>
<field name="list_price">0.00</field>
<field name="weight">0.00</field>
<field name="type">consu</field>
<field name="categ_id" ref="product.product_category_services"/>
<field name="uom_id" ref="uom.product_uom_unit"/>
<field name="default_code">DISC</field>
<field name="purchase_ok">False</field>
</record>
```
The error occurs because the user deleted the category and then installed `pos_discount` and `pos_sale` modules, which reference the missing product category.
This commit resolves the error by providing a False value for the field if the product category is missing.
sentry-6291223593
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#197435When we ask for a reimbursement for the VAT that is due from the state, we close the period, then we send the declarations, with the amount that is asked as reimbursement. The issue is that we need this amount to be registered in the report of this period. But it is closed, so we can't post moves with the tag in it. Let's transform it into an external value. task-4328721 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: od
Original PR description
When we ask for a reimbursement for the VAT that is due from the state, we close the period, then we send the declarations, with the amount that is asked as reimbursement. The issue is that we need this amount to be registered in the report of this period. But it is closed, so we can't post moves with the tag in it. Let's transform it into an external value. task-4328721 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197642 Forward-Port-Of: odoo/odoo#193529
The Chart of Accounts sidebar does not display account group codes due to the limit being set to `0`. In earlier versions, `limit="0"` was used to indicate no limit at all, as the default value (`200`) was not sufficient. However, in version 18.1, a change in the Odoo framework introduced a stricter limit check in this [commit](https://github.com/odoo/odoo/blob/88dff02bae41ff794ac3e60acab061acfc8e19ca/odoo/orm/models.py#L5596-L5597). With this update, `limit=0` is now interpreted as a **h
Original PR description
The Chart of Accounts sidebar does not display account group codes due to the limit being set to `0`. In earlier versions, `limit="0"` was used to indicate no limit at all, as the default value…
The Chart of Accounts sidebar does not display account group codes due to the limit being set to `0`. In earlier versions, `limit="0"` was used to indicate no limit at all, as the default value (`200`) was not sufficient. However, in version 18.1, a change in the Odoo framework introduced a stricter limit check in this [commit](https://github.com/odoo/odoo/blob/88dff02bae41ff794ac3e60acab061acfc8e19ca/odoo/orm/models.py#L5596-L5597). With this update, `limit=0` is now interpreted as a **hard limit of zero records**, meaning nothing is retrieved from the dataset. As a result, account groups no longer appear in the sidebar. Previously, `limit="0"` would effectively disable any limit. To achieve the same behavior in 18.1+, `limit` must be explicitly set to `False` or `None`. Steps to Reproduce: 1. Navigate to Accounting → Configurations → Chart of Accounts. 2. Observe that the account group codes are missing from the sidebar. opw-4538769 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197363
To reproduce: Testing `test_ensure_correct_website_asset` with multiple website will consistently fail as the bundle from the biggest `website_id` is used whereas it compare the bundle to default website loaded, which looks to be the one with the smallest ID. Installing `test_themes` reproduce the issue consistently as the website with biggest and smallest ID will use different theme website with distinct bundle After this fix: As the website with smaller ID load by default, we use the
Original PR description
To reproduce: Testing `test_ensure_correct_website_asset` with multiple website will consistently fail as the bundle from the biggest `website_id` is used whereas it compare the bundle to default website loaded, which looks to be the one with the smallest ID. Installing `test_themes` reproduce the issue consistently as the website with biggest and smallest ID will use different theme website with distinct bundle After this fix: As the website with smaller ID load by default, we use the smallest existing website_id rather than the biggest one rb-65788 Forward-Port-Of: odoo/odoo#198006
Before this commit, the PoS notes were not displayed in the correct order in the PoS interface, despite the existence of a `sequence` field that allowed users to define their desired order. opw-4473463 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#193789
Original PR description
Before this commit, the PoS notes were not displayed in the correct order in the PoS interface, despite the existence of a `sequence` field that allowed users to define their desired order. opw-4473463 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#193789
Purpose of this commit: The command descriptions (canned responses, channel command) currently use an italic font style due to being wrapped in the emphasis tag, causing the text to appear cropped at the end of the sentence. This commit resolves the issue by replacing the emphasis tag with a span tag. task-4485553 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#198229 Forward-Port-Of: odoo/odoo#193915
Original PR description
Purpose of this commit: The command descriptions (canned responses, channel command) currently use an italic font style due to being wrapped in the emphasis tag, causing the text to appear cropped at the end of the sentence. This commit resolves the issue by replacing the emphasis tag with a span tag. task-4485553 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#198229 Forward-Port-Of: odoo/odoo#193915
Nilvera requires the country name in the XML to be in Turkish. To achieve this, the Turkish language is now activated during installation, ensuring translated values are stored in the database and can be enforced in the XML output. task-4504454 Forward-Port-Of: odoo/odoo#197933
Original PR description
Nilvera requires the country name in the XML to be in Turkish. To achieve this, the Turkish language is now activated during installation, ensuring translated values are stored in the database and can be enforced in the XML output. task-4504454 Forward-Port-Of: odoo/odoo#197933
In the following HTML: ```html <h1>[test</h1><p>content]</p>\n ``` The "\n" text node is invisible whitespace. When deleting the selection, failing to account for that, the content of the heading was "joined" with the invisible text node so that the heading's first child was that text node. This enventually snowballed when inserting new content as the start container was now a text node at offset 0, signalling to `insert` to do its insertion before its parent, and we ended up with an emp
Original PR description
In the following HTML: ```html <h1>[test</h1><p>content]</p>\n ``` The "\n" text node is invisible whitespace. When deleting the selection, failing to account for that, the content of the heading was…
In the following HTML: ```html <h1>[test</h1><p>content]</p>\n ``` The "\n" text node is invisible whitespace. When deleting the selection, failing to account for that, the content of the heading was "joined" with the invisible text node so that the heading's first child was that text node. This enventually snowballed when inserting new content as the start container was now a text node at offset 0, signalling to `insert` to do its insertion before its parent, and we ended up with an empty block after our insertion. This fixes it by correcting `getJoinableFragment` so it doesn't join with an invisible text node. ----- This prevents the default behavior of a mousedown event on the ChatGPT alternatives dialog so it doesn't cancel the user's text selection in the editor. This way, like with every other dialog, whenever it's open nothing can happen in the background. task-4258167 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186122
In 50c62eab72678d51fb88c88fbeb81da2decca6f2, an override was done to attachments to disable deleting them, detaching them instead. As this is only required for German companies, a check can be added in the override to allow non-German companies to be able to delete their attachments. Also, another restriction was added for changing the fiscal country to make sure the flow for deleting German attachments cannot be bypassed. task-4500319 Forward-Port-Of: odoo/odoo#198062 Forward-Port-Of: odoo/
Original PR description
In 50c62eab72678d51fb88c88fbeb81da2decca6f2, an override was done to attachments to disable deleting them, detaching them instead. As this is only required for German companies, a check can be added in the override to allow non-German companies to be able to delete their attachments. Also, another restriction was added for changing the fiscal country to make sure the flow for deleting German attachments cannot be bypassed. task-4500319 Forward-Port-Of: odoo/odoo#198062 Forward-Port-Of: odoo/odoo#197006
Description of the issue/feature this PR addresses: In the 'CONTRIBUTING.md' file , there is a list item with the text: > Use this **template** when reporting issues. Please search for duplicates first! The link named 'template' should point to a pull request template. Current behavior before PR: The link named 'template' is broken and give a 404 error. Desired behavior after PR is merged: The link named 'template' now target the 'Contributing' wiki page, section 'making-p
Original PR description
Description of the issue/feature this PR addresses: In the 'CONTRIBUTING.md' file , there is a list item with the text: > Use this **template** when reporting issues. Please search for duplicates first! The link named 'template' should point to a pull request template. Current behavior before PR: The link named 'template' is broken and give a 404 error. Desired behavior after PR is merged: The link named 'template' now target the 'Contributing' wiki page, section 'making-pull-request' that contains the desired template. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197547
**Current behavior before PR:** When dragging and dropping selected content excluding images in the editor, the content was duplicated at the new location, leaving the original content intact. **Desired behavior after PR is merged:** Dragging and dropping selected content now removes it from its original location and places it in the new location, effectively functioning as a cut and paste operation. task:4369910 Forward-Port-Of: odoo/odoo#189672
Original PR description
**Current behavior before PR:** When dragging and dropping selected content excluding images in the editor, the content was duplicated at the new location, leaving the original content intact. **Desired behavior after PR is merged:** Dragging and dropping selected content now removes it from its original location and places it in the new location, effectively functioning as a cut and paste operation. task:4369910 Forward-Port-Of: odoo/odoo#189672
Before this commit: Using the button command in the powerbox resulted in the creation of a regular link instead of a button. After this commit: Executing the button command now correctly creates a primary button as intended. task-4380129 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189893
Original PR description
Before this commit: Using the button command in the powerbox resulted in the creation of a regular link instead of a button. After this commit: Executing the button command now correctly creates a primary button as intended. task-4380129 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#189893
**Current behavior before PR:** When there is a `heading`, `pre` or `blockquote` tag in `rtl` direction, pressing enter at the end of element creates a new `p` tag in `ltr` direction rather than `rtl`. **Desired behavior after PR:** Now, pressing enter at the end of `heading`, `pre` or `blockquote` tag in `rtl` direction creates a new empty paragraph tag with `rtl` direction. task-4484619 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Original PR description
**Current behavior before PR:** When there is a `heading`, `pre` or `blockquote` tag in `rtl` direction, pressing enter at the end of element creates a new `p` tag in `ltr` direction rather than `rtl`. **Desired behavior after PR:** Now, pressing enter at the end of `heading`, `pre` or `blockquote` tag in `rtl` direction creates a new empty paragraph tag with `rtl` direction. task-4484619 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#194463
When the user opens the PoS interfaces from the backend, the PoS will perform a request to get changed data. taskId: 4547439 Forward-Port-Of: odoo/odoo#197204
Original PR description
When the user opens the PoS interfaces from the backend, the PoS will perform a request to get changed data. taskId: 4547439 Forward-Port-Of: odoo/odoo#197204
Fix issue generating traceback where when merging floating orders together. As `mergeOrders` can be used with floating orders, it doesn't necessarily contain a table. A check has been added to handle this case properly. After selecting an order to merge with, we now also redirect to this order. Steps to reproduce: - Create new floating order - Add items to the cart - Click "Set Tab" - Select existing floating orders task-id: 4551788 Description of the issue/feature this PR addresses
Original PR description
Fix issue generating traceback where when merging floating orders together. As `mergeOrders` can be used with floating orders, it doesn't necessarily contain a table. A check has been added to handle this case properly. After selecting an order to merge with, we now also redirect to this order. Steps to reproduce: - Create new floating order - Add items to the cart - Click "Set Tab" - Select existing floating orders task-id: 4551788 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#196744
Inside the dialog used to connect to a database, the instruction were confusing. They have been simplified to 2 basic instructions, easy to follow. Task: 4585446  Forward-Port-Of: odoo/odoo#198150
Original PR description
Inside the dialog used to connect to a database, the instruction were confusing. They have been simplified to 2 basic instructions, easy to follow. Task: 4585446  Forward-Port-Of: odoo/odoo#198150
Purpose: -------- Replace the usage of the savepoints introduced in [this commit](https://github.com/odoo/odoo/commit/e7271331ee52596e307f402b76ff61b58ec59429) which might lead to poor performances. See https://github.com/odoo/odoo/pull/167236 for more details. Since commit and rollback are forbidden in tests, the part in the `test_scheduled_message_posting` test checking that the failed scheduled message was not posted has been removed. Task-4575344 Forward-Port-Of: odoo/odoo#197855 F
Original PR description
Purpose: -------- Replace the usage of the savepoints introduced in [this commit](https://github.com/odoo/odoo/commit/e7271331ee52596e307f402b76ff61b58ec59429) which might lead to poor performances. See https://github.com/odoo/odoo/pull/167236 for more details. Since commit and rollback are forbidden in tests, the part in the `test_scheduled_message_posting` test checking that the failed scheduled message was not posted has been removed. Task-4575344 Forward-Port-Of: odoo/odoo#197855 Forward-Port-Of: odoo/odoo#197614
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#198001
Original PR description
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#198001
[FIX] l10n{latam_invoice_document,hu_edi}: layout header & footer issues Bubble and wave layout footer content of l10n_ar edi invoice qr code was a little bit cut off in preview. In addition when you had both, `l10n_hu_edi` and `l10n_latam_invoice_document` installed, you would have a double header/footer. And the header of bubble/wave layout does not have the bubble/wave. Last, there is some space between the document and the "shadow" of the document in portal preview which looks wei
Original PR description
[FIX] l10n{latam_invoice_document,hu_edi}: layout header & footer issues Bubble and wave layout footer content of l10n_ar edi invoice qr code was a little bit cut off in preview. In addition when you…
[FIX] l10n{latam_invoice_document,hu_edi}: layout header & footer issues
Bubble and wave layout footer content of l10n_ar edi invoice qr code
was a little bit cut off in preview. In addition when you had both,
`l10n_hu_edi` and `l10n_latam_invoice_document` installed, you would
have a double header/footer. And the header of bubble/wave layout
does not have the bubble/wave. Last, there is some space between the
document and the "shadow" of the document in portal preview which
looks weird when the selected layout is bubble or wave which normally
goes all the way until the margins.
How to reproduce:
- install l10n_latam_invoice_document
- move to (AR) Responsable Inscripto" company
- Switch Document Layout to "Bubble" format
- Create an invoice with B2B customer
- make sure the Document Type is set to "(1) INVOICES A".
- Make sure the Journal is "Electronic Invoice"
- Validate the invoice
- Click on Preview button
What's wrong here:
1. At the bottom of the invoice, the CAE and CAE Due Date fields are
cropped
2. Also if you installed l10n_hu_edi, you will have a double
header/footer
3. The header does not have the bubble
4. The bubble doesn't go all way until the margins in portal preview
Regarding the first issue, this commit fixes it by moving
the custom footer to `o_content_footer` instead of it replacing the
whole footer. This was done for all `l10n_hu_edi` layouts as well as
`l10n_latam_invoice_document` layouts for consistency
For the second double header/footer issue, added a check before
overriding:
- company._name == 'res.company' to avoid breaking Configure Document
Layout wizard (there the `comptany` is of model `base.document.layout`
- only override if fiscal country corresponds to that of the localisation
And for the last issue with header not rendering as expected, this
commit uses another xpath for header overriding as in
[#192650](https://github.com/odoo/odoo/pull/192650)
opw-4411237
Forward-Port-Of: odoo/odoo#192485**Current behavior before PR:** Previously, the shortcut was triggered using `:shortcut`, which has now been updated to `::shortcut` on /help command. **Desired behavior after PR is merged:** to align with the new trigger format for canned responses it is changed to `::shortcut`. Additionally, a message has been added: 'Type :emoji: to insert an emoji in your message' to help users. task-4531300 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/subm
Original PR description
**Current behavior before PR:** Previously, the shortcut was triggered using `:shortcut`, which has now been updated to `::shortcut` on /help command. **Desired behavior after PR is merged:** to align with the new trigger format for canned responses it is changed to `::shortcut`. Additionally, a message has been added: 'Type :emoji: to insert an emoji in your message' to help users. task-4531300 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#196136
Since Odoo 18.0, the recipient is always included when sending a simplified invoice. While this is allowed by TicketBAI, it is only valid if the partner has a VAT number (NIF). Steps to reproduce: Install the l10n_es_edi_tbai module and setup an ES company Create a simplified invoice with the partner "Simplified Invoice Partner (ES)" Send the invoice to TicketBAI The following error will be returned: "B4_1000002: Todos los registros incluidos en la petición son incorrectos." The Fix:
Original PR description
Since Odoo 18.0, the recipient is always included when sending a simplified invoice. While this is allowed by TicketBAI, it is only valid if the partner has a VAT number (NIF). Steps to reproduce: Install the l10n_es_edi_tbai module and setup an ES company Create a simplified invoice with the partner "Simplified Invoice Partner (ES)" Send the invoice to TicketBAI The following error will be returned: "B4_1000002: Todos los registros incluidos en la petición son incorrectos." The Fix: For simplified invoices, this fix ensures that the recipient is only included in the XML if the partner has a VAT/NIF. If not, the recipient is omitted to avoid TicketBAI validation errors. Ticket [link 1](https://www.odoo.com/odoo/project/967/tasks/4525875), [link 2](https://www.odoo.com/odoo/project/967/tasks/4522938), [link 3](https://www.odoo.com/odoo/project/967/tasks/4553030) opw-4525875 opw-4522938 opw-4553030 Forward-Port-Of: odoo/odoo#197472
Before this commit, when archiving an inheriting view from a main one (via the list and the form), the main record was not savable. This is due to 6f06420e4a9443c52dc0cb427f8f55eb4aecabce which automatically adds missing but useful fields in a view in readonly mode. This commit adds that field manually to be able to save the active field. opw-4534225 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ---
Original PR description
Before this commit, when archiving an inheriting view from a main one (via the list and the form), the main record was not savable. This is due to 6f06420e4a9443c52dc0cb427f8f55eb4aecabce which automatically adds missing but useful fields in a view in readonly mode. This commit adds that field manually to be able to save the active field. opw-4534225 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#197992 Forward-Port-Of: odoo/odoo#197137
Forward-Port-Of: odoo/odoo#198125
Original PR description
Forward-Port-Of: odoo/odoo#198125
Accrual plans are not readable for regular users, so once a user has an accrual plan set on one of their allocations, they cannot open their time off dashboard. Access rights error gets thrown. The bug was supposedly fixed in commit: https://github.com/odoo/odoo/commit/30f7fe62ef2579ed0a0c3ad9dbec5edf2ca60b18 but it did not consider adding the sudo() for the condition based on the carryover_policy. Steps to Reproduce on Runbot: As Mitchell Admin: 1. Install Time Off app 2. Create a time
Original PR description
Accrual plans are not readable for regular users, so once a user has an accrual plan set on one of their allocations, they cannot open their time off dashboard. Access rights error gets thrown. The…
Accrual plans are not readable for regular users, so once a user has an accrual plan set on one of their allocations, they cannot open their time off dashboard. Access rights error gets thrown. The bug was supposedly fixed in commit: https://github.com/odoo/odoo/commit/30f7fe62ef2579ed0a0c3ad9dbec5edf2ca60b18 but it did not consider adding the sudo() for the condition based on the carryover_policy. Steps to Reproduce on Runbot: As Mitchell Admin: 1. Install Time Off app 2. Create a time off type (show in dashboard,requires allocation) 3. Create an accrual plan (accrued_gain_time: end, carryover_date: year_start) 4. Create a rule for the accrual plan (Accumulate 0.5 days, month at the 1st of the month, carryover policy is either none or maximum) 5. Create an allocation for Marc Demo,who has no time off rights, for the time off type. Set to accrual allocation and link to the accrual plan.Then, set the start date to the 1st of the month and run until some future date. As Marc Demo: 1. Attempt to click into the Time Off app 2. Observe Access Right error opw-4551392 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197069
Problem: When a non-admin user tries to send an invoice by email or print an invoice report, an access error is thrown because the fields l10n_id_qris_api_key and l10n_id_qris_mid are locked behind the Admin/Settings group. Purpose: Non-admin users should be able to send and print invoices regardless of their admin rights. Apply sudo when accessing those specific fields. Steps to reproduce on Runbot: ADMIN 1. Install Contacts, Accounting, l10n_id 2. Enable QR Codes in Settings > Account
Original PR description
Problem: When a non-admin user tries to send an invoice by email or print an invoice report, an access error is thrown because the fields l10n_id_qris_api_key and l10n_id_qris_mid are locked behind the Admin/Settings group. Purpose: Non-admin users should be able to send and print invoices regardless of their admin rights. Apply sudo when accessing those specific fields. Steps to reproduce on Runbot: ADMIN 1. Install Contacts, Accounting, l10n_id 2. Enable QR Codes in Settings > Accounting 3. Give Marc Demo basic accounting and bank rights, but no admin rights MARC DEMO 1. Switch to ID Company 2. Create and confirm invoice 3. Attempt to send and/or print invoice 4. Access Error is thrown opw-4529074 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#197706
The following PR: https://github.com/odoo/odoo/pull/190321 introduced a new website tour. However, one of the step make the tour consistently fail with a single app website install. The reason for the fail is that the "edit link" sub-window is opened by default if the link is not open through the "extra menu". Clicking the button (what currently do the test) do close the sub-window making the input not clickable in the following step. ![image](https://github.com/user-attachments/assets/ee
Original PR description
The following PR: https://github.com/odoo/odoo/pull/190321 introduced a new website tour. However, one of the step make the tour consistently fail with a single app website install. The reason for…
The following PR: https://github.com/odoo/odoo/pull/190321 introduced a new website tour. However, one of the step make the tour consistently fail with a single app website install. The reason for the fail is that the "edit link" sub-window is opened by default if the link is not open through the "extra menu". Clicking the button (what currently do the test) do close the sub-window making the input not clickable in the following step.  *single-app website build screenshot* the URL input is open by default *multi-app build screenshot* the URL input is not shown by default as the mega-menu menu-item is shown in the "extra menu" due to the amount of menu added by other website related app After this PR: The "edit link" button is pressed only if the input is not visible rb-111286 Forward-Port-Of: odoo/odoo#197757
Before this commit, when using spreadsheet with some chat bubbles, the chat bubbles were cut with horizontal scrollbar of spreadsheet. Steps to reproduce: - make a spreadsheet - put a chat in chat bubble (e.g. from click on messaging menu) - remove the "filters" panel of the spreadsheet This happens because the horizontal scrollbar of spreadsheet uses a `z-index: 15` while chat bubble uses `z-index: 10`. The `z-index` of chat bubble is relative to navigable list, and since the value
Original PR description
Before this commit, when using spreadsheet with some chat bubbles, the chat bubbles were cut with horizontal scrollbar of spreadsheet. Steps to reproduce: - make a spreadsheet - put a chat in chat…
Before this commit, when using spreadsheet with some chat bubbles, the chat bubbles were cut with horizontal scrollbar of spreadsheet. Steps to reproduce: - make a spreadsheet - put a chat in chat bubble (e.g. from click on messaging menu) - remove the "filters" panel of the spreadsheet This happens because the horizontal scrollbar of spreadsheet uses a `z-index: 15` while chat bubble uses `z-index: 10`. The `z-index` of chat bubble is relative to navigable list, and since the value was exactly slightly offset from navigable list, this commit fixes by shifting the `$o-mail-NavigableList-zIndex`. It was `11`, now it's `21`. As a result, the chat bubble `z-index` is being changed from `10` to `20`, which is greater to `15` from spreadsheet horizontal scrollbar. Task-4547672 Before / After <img width="106" alt="Screenshot 2025-02-17 at 17 10 28" src="https://github.com/user-attachments/assets/caf3d9f8-59d4-4b2b-9981-d2e5ed68a510" /> <img width="97" alt="Screenshot 2025-02-17 at 17 11 14" src="https://github.com/user-attachments/assets/1c9376bc-ca24-42dd-8864-eee0878fc1c7" /> Forward-Port-Of: odoo/odoo#198021
This commit comes as an apology for the horrible code I wrote in PR #166043 in order for the installation of `l10n_hu_edi` to not fail if some of the default Hungarian taxes (defined in `l10n_hu`) had been deleted. Instead of rolling back the loading of the EDI-specific fields if some taxes don't exist, we can just load those fields on the taxes that do exist. Which is a lot cleaner and simpler. Sorry again! task-none Forward-Port-Of: odoo/odoo#196471
Original PR description
This commit comes as an apology for the horrible code I wrote in PR #166043 in order for the installation of `l10n_hu_edi` to not fail if some of the default Hungarian taxes (defined in `l10n_hu`) had been deleted. Instead of rolling back the loading of the EDI-specific fields if some taxes don't exist, we can just load those fields on the taxes that do exist. Which is a lot cleaner and simpler. Sorry again! task-none Forward-Port-Of: odoo/odoo#196471
The `PreparationPrinterContent` test was checking if the preparation receipt was containing a specific string. But the check was performed on the `.render-container` which is generated for printing and erased just after. That was causing a random error in the test. Now we call internal `pos_store` method that generate the receipt content and we check if the string is present in the content. runbot error id: 114884 Forward-Port-Of: odoo/odoo#197340 Forward-Port-Of: odoo/odoo#197212
Original PR description
The `PreparationPrinterContent` test was checking if the preparation receipt was containing a specific string. But the check was performed on the `.render-container` which is generated for printing and erased just after. That was causing a random error in the test. Now we call internal `pos_store` method that generate the receipt content and we check if the string is present in the content. runbot error id: 114884 Forward-Port-Of: odoo/odoo#197340 Forward-Port-Of: odoo/odoo#197212
Before this commit, since https://github.com/odoo/odoo/pull/189657, the mobile push-to-talk button was also affected by the aspect ratio affecting all buttons of the call action list. This was making the button too big and covering the whole call view. This commit fixes this issue by introducing a dedicated selector for the bar part of the call action list. before:  after:  after:  Forward-Port-Of: odoo/odoo#197884
Before this PR, the visitor offline banner could be shown to the visitor. The condition used to determine whether the banner should be shown is incorrect (it compares channel member to persona). At the same time, this PR cleans the thread component patch: the component relies on the `useEffect` hook to update a state based on the persona im status. The only purpose of this method is to delay the update in the UI to avoid flicker during quick disconnects. However, a debounce is already in p
Original PR description
Before this PR, the visitor offline banner could be shown to the visitor. The condition used to determine whether the banner should be shown is incorrect (it compares channel member to persona). At the same time, this PR cleans the thread component patch: the component relies on the `useEffect` hook to update a state based on the persona im status. The only purpose of this method is to delay the update in the UI to avoid flicker during quick disconnects. However, a debounce is already in place in the persona model. Other places in the UI might be impacted by the same flickers, so we better increase de debounce delay directly in the model setter. It also remove the need for complex code in the component. 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#198072
### Steps to reproduce: - Go to an invoice - Click "Send" - Try to add a new attachment - Traceback ### Cause: The template of `mail_attachments_selector` is a template from the module `mail`. In this [commit](https://github.com/odoo/odoo/commit/fbc21577c01b07d677b5f6d2784f42d3b3caf84e#diff-20933689544fe18977505a4bcd6222eacd92376dea482d9e3246b9a0c41d5fdd) the template was changed to use the component `FileHandler` instead of `FileInput` and the corresponding `onFileUploaded` was changed
Original PR description
### Steps to reproduce: - Go to an invoice - Click "Send" - Try to add a new attachment - Traceback ### Cause: The template of `mail_attachments_selector` is a template from the module `mail`. In this [commit](https://github.com/odoo/odoo/commit/fbc21577c01b07d677b5f6d2784f42d3b3caf84e#diff-20933689544fe18977505a4bcd6222eacd92376dea482d9e3246b9a0c41d5fdd) the template was changed to use the component `FileHandler` instead of `FileInput` and the corresponding `onFileUploaded` was changed but not the one from the `account` module. This method was receiving objects but expected a list which explains the error. ### Solution: Update the function to mirror the [one](https://github.com/odoo/odoo/blob/5d67ca906bfd1f25f7c831a7fcc6359cfaa7a9a6/addons/mail/static/src/core/web/mail_composer_attachment_selector.js#L24-L35) from the component's JS file. opw-4559421 Forward-Port-Of: odoo/odoo#197753
This PR introduces a class on the livechat-root element when livechat button is displayed to the visitor. task-4567743 Forward-Port-Of: odoo/odoo#197572
Original PR description
This PR introduces a class on the livechat-root element when livechat button is displayed to the visitor. task-4567743 Forward-Port-Of: odoo/odoo#197572
Have a many2many_tags widget with `edit_tags` option enabled. Click on a tag to edit it, make a change in the dialog and click save. Before this commit, for the change to be reflected in the tag, we generated a forget command (3), followed by a link_to (4). As already pointed out here [1], this hack had some drawbacks: the tag order was lost upon edition, as the edited tag was moved to the end. There was another problem. For one2many fields whose corresponding many2one has constraint `onde
Original PR description
Have a many2many_tags widget with `edit_tags` option enabled. Click on a tag to edit it, make a change in the dialog and click save. Before this commit, for the change to be reflected in the tag, we…
Have a many2many_tags widget with `edit_tags` option enabled. Click on a tag to edit it, make a change in the dialog and click save. Before this commit, for the change to be reflected in the tag, we generated a forget command (3), followed by a link_to (4). As already pointed out here [1], this hack had some drawbacks: the tag order was lost upon edition, as the edited tag was moved to the end. There was another problem. For one2many fields whose corresponding many2one has constraint `ondelete cascade`, commands 3 are treated like commands delete (2). As a consequence, in that kind of setup, editing a tag actually deleted it. To fix those issues, this commit simply forces a reload of the edited tag, instead using the commands 3 and 4. [1] https://github.com/odoo/odoo/pull/165935#pullrequestreview-2068519552 Task-4567058 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#198083
Before this commit: The version set on an IoT box server side would never update as it was set only on creation. Also took the opportunity to refactor a bit this old part of the code to make it clearer and add some relevant logs to more easily investigate cases where it could be relevant After this commit: IoT version will now appear with the real value on the IoT app & beautiful relevant logs  *before this PR, the IoT would be stuck with the wrong version (here 18.0)*  *after this PR*  *logs example* opw-4502002 Forward-Port-Of: odoo/enterprise#79603
During the execution of the validation cron of the OCR, the IAP account selected could sometimes be incorrect. In the context of the validation cron, we need to know to which company the document belong in order to get the correct IAP account (i.e. the one from the company, if it exists). If we use the generic IAP account (i.e. the one that isn't linked to any company), the mismatch of accounts will cause the validation to be ignored by the OCR server. Related ticket [#4522628](https://
Original PR description
During the execution of the validation cron of the OCR, the IAP account selected could sometimes be incorrect. In the context of the validation cron, we need to know to which company the document belong in order to get the correct IAP account (i.e. the one from the company, if it exists). If we use the generic IAP account (i.e. the one that isn't linked to any company), the mismatch of accounts will cause the validation to be ignored by the OCR server. Related ticket [#4522628](https://www.odoo.com/odoo/project.task/4522628) Forward-Port-Of: odoo/enterprise#79550 Forward-Port-Of: odoo/enterprise#79525
Details in various commits Forward-Port-Of: odoo/enterprise#79533
Original PR description
Details in various commits Forward-Port-Of: odoo/enterprise#79533
Impact on enterprise. We do not want to get records that don't have any roles as before the fix, False was ignored in x2m fields. odoo/odoo#197890 Forward-Port-Of: odoo/enterprise#79593
Original PR description
Impact on enterprise. We do not want to get records that don't have any roles as before the fix, False was ignored in x2m fields. odoo/odoo#197890 Forward-Port-Of: odoo/enterprise#79593
The declaration 3519 is also needed when we ask for a reimbursement. We currently can't group them (as the fields definition don't allow it), so we will keep them separated. It is sent the same way to AspOne. task-4328721 Forward-Port-Of: odoo/enterprise#79274 Forward-Port-Of: odoo/enterprise#77104
Original PR description
The declaration 3519 is also needed when we ask for a reimbursement. We currently can't group them (as the fields definition don't allow it), so we will keep them separated. It is sent the same way to AspOne. task-4328721 Forward-Port-Of: odoo/enterprise#79274 Forward-Port-Of: odoo/enterprise#77104
This commit fix 2 columns in the Libro de IVA xlsx export file: 1. **expense_series_number**: before it was the move name, now it's the move ref 2. **reception_number**: before it was blank, now it's the move name task-4508992 Forward-Port-Of: odoo/enterprise#79459
Original PR description
This commit fix 2 columns in the Libro de IVA xlsx export file: 1. **expense_series_number**: before it was the move name, now it's the move ref 2. **reception_number**: before it was blank, now it's the move name task-4508992 Forward-Port-Of: odoo/enterprise#79459
In this commit: === - Adjusted the UI to align with the newly merged POS design. - Ensured that all elements related to UrbanPiper online orders are displayed correctly and without overlapping issues. task-4446972 Forward-Port-Of: odoo/enterprise#76447
Original PR description
In this commit: === - Adjusted the UI to align with the newly merged POS design. - Ensured that all elements related to UrbanPiper online orders are displayed correctly and without overlapping issues. task-4446972 Forward-Port-Of: odoo/enterprise#76447
Mod349 tax report in Spanish localization should report the total number of intra-community operators [1] However currently we count the number of operations Steps to reproduce: - With an ES company setup - Create 2 invoice to the same an EU partner - Go to Accounting / Reporting / Statement Reports / Tax Report - Select Tax Report (Mod 349) (ES) Issue: Total number of intra-community operators is 2, but should be 1 [1] https://sede.agenciatributaria.gob.es/static_files/Sede/Proced
Original PR description
Mod349 tax report in Spanish localization should report the total number of intra-community operators [1] However currently we count the number of operations Steps to reproduce: - With an ES company setup - Create 2 invoice to the same an EU partner - Go to Accounting / Reporting / Statement Reports / Tax Report - Select Tax Report (Mod 349) (ES) Issue: Total number of intra-community operators is 2, but should be 1 [1] https://sede.agenciatributaria.gob.es/static_files/Sede/Procedimiento_ayuda/GI28/instr_mod_349.pdf opw-4403287 Forward-Port-Of: odoo/enterprise#79522 Forward-Port-Of: odoo/enterprise#78588
Customer statement can be accessed from the partner record and eventually sent to the customer. However currently the mail wizard will add 2 signatures at the end of the mail Steps to reproduce: - Open a partner - Access Customer Statement - Click Print, send email - Check sent email Issue: The signature is duplicated opw-4456798 Forward-Port-Of: odoo/enterprise#79389
Original PR description
Customer statement can be accessed from the partner record and eventually sent to the customer. However currently the mail wizard will add 2 signatures at the end of the mail Steps to reproduce: - Open a partner - Access Customer Statement - Click Print, send email - Check sent email Issue: The signature is duplicated opw-4456798 Forward-Port-Of: odoo/enterprise#79389
- make `new_car` True by default if the `available_cars_amount` is less than the `max_unused_cars` Task: 4378810 Forward-Port-Of: odoo/enterprise#79537 Forward-Port-Of: odoo/enterprise#75876
Original PR description
- make `new_car` True by default if the `available_cars_amount` is less than the `max_unused_cars` Task: 4378810 Forward-Port-Of: odoo/enterprise#79537 Forward-Port-Of: odoo/enterprise#75876
- update the `co2_fee_min, health_indice` paramters values Task: 4563950 Forward-Port-Of: odoo/enterprise#79523 Forward-Port-Of: odoo/enterprise#78999
Original PR description
- update the `co2_fee_min, health_indice` paramters values Task: 4563950 Forward-Port-Of: odoo/enterprise#79523 Forward-Port-Of: odoo/enterprise#78999
This commit adds some QoL improvements on l10n_uy_edi when creating an Uruware testing account, as listed: - if in test mode, skip the uuid validation - if in test mode, use the current user email address for the contact for Uruware to send the credentials - in the successful event notification, display the email address where the credentials will be sent from Uruware - add cooldown period of 24 hours everytime a successful request for creating uruware account is sent related IAP PR: ht
Original PR description
This commit adds some QoL improvements on l10n_uy_edi when creating an Uruware testing account, as listed: - if in test mode, skip the uuid validation - if in test mode, use the current user email address for the contact for Uruware to send the credentials - in the successful event notification, display the email address where the credentials will be sent from Uruware - add cooldown period of 24 hours everytime a successful request for creating uruware account is sent related IAP PR: https://github.com/odoo/iap-apps/pull/974 task-id: 4411564 Forward-Port-Of: odoo/enterprise#79387 Forward-Port-Of: odoo/enterprise#78008
Clicking 'Name this version' in the version history panel causes a traceback because the `el` of TextInput is not found. We have two possible solutions: 1. Forward the refs of TextInput and VersionHistoryItem explicitly using `useChildRef` and `useForwardRefToParent`, or use a callback to retrieve the ref for focusing the input. 2. Remove the menu item, as the cursor already changes to a text pointer on hover, indicating the name is editable. I think the second approach is better since
Original PR description
Clicking 'Name this version' in the version history panel causes a traceback because the `el` of TextInput is not found. We have two possible solutions: 1. Forward the refs of TextInput and VersionHistoryItem explicitly using `useChildRef` and `useForwardRefToParent`, or use a callback to retrieve the ref for focusing the input. 2. Remove the menu item, as the cursor already changes to a text pointer on hover, indicating the name is editable. I think the second approach is better since it is simpler and more intuitive. Task: 4563422 Forward-Port-Of: odoo/enterprise#79474
Currently a `ParseError` arises when the user installs the `appointment_account_payment` module after deleting the `Service` category in `Invoicing`. Steps to reproduce: --- - Install `Invoicing` application (without demo data) - Invoicing > Configuration > Categories > Delete `Services` - Now install `appointment_account_payment` module Traceback: --- ``` ValueError: External ID not found in the system: product.product_category_services ParseError: while parsing /home/odoo/src/e
Original PR description
Currently a `ParseError` arises when the user installs the `appointment_account_payment` module after deleting the `Service` category in `Invoicing`. Steps to reproduce: --- - Install `Invoicing`…
Currently a `ParseError` arises when the user installs the `appointment_account_payment` module after deleting the `Service` category in `Invoicing`.
Steps to reproduce:
---
- Install `Invoicing` application (without demo data)
- Invoicing > Configuration > Categories > Delete `Services`
- Now install `appointment_account_payment` module
Traceback:
---
```
ValueError: External ID not found in the system: product.product_category_services
ParseError: while parsing /home/odoo/src/enterprise/saas-18.1/appointment_account_payment/data/product_data.xml:3, somewhere inside <record id="default_booking_product" model="product.product">
<field name="name">Booking Fees</field>
<field name="standard_price">0.00</field>
<field name="uom_id" ref="uom.product_uom_unit"/>
<field name="list_price">50.00</field>
<field name="type">service</field>
<field name="purchase_ok" eval="False"/>
<field name="categ_id" ref="product.product_category_services"/>
<field name="image_1920" type="base64" file="appointment_account_payment/static/src/img/booking_product.png"/>
</record>
```
The error occurs because the user deleted the category and then installed the `appointment_account_payment` module, which references the missing product category.
This commit resolves the error by providing a False value for the field if the product category is missing.
sentry-6298992760
Forward-Port-Of: odoo/enterprise#79365Steps to reproduce ================== - Got to appointment type; - Apply some filter. - Now create a share link. - Filter is lost. Technical =========== https://github.com/odoo/enterprise/pull/63046/commits/492296e91e9c0b1106a7bc6852010be426d2abe8 Here we are loading the action while creating or updating the share link to reflect the changes without refreshing. It is not required when we create a share link from other places instead of a Share link menu. After this commit ========
Original PR description
Steps to reproduce ================== - Got to appointment type; - Apply some filter. - Now create a share link. - Filter is lost. Technical =========== https://github.com/odoo/enterprise/pull/63046/commits/492296e91e9c0b1106a7bc6852010be426d2abe8 Here we are loading the action while creating or updating the share link to reflect the changes without refreshing. It is not required when we create a share link from other places instead of a Share link menu. After this commit ================== This commit addresses the issue and now the filter will not lost when we create a share link from appointment_type. Task-4138356 Forward-Port-Of: odoo/enterprise#71165
The items inside the wizard view are ordered as a 2 column grid of labels and contents. But recently, it is found that the hard lock date alert item is only displayed in the short label section of the grid. This commit spans the hard lock date `div`'s `colspan` to 2 to make sure it spans on the whole line. for more info:  task-4586675 Forward-Port-Of: odoo/enterprise#79572
Original PR description
The items inside the wizard view are ordered as a 2 column grid of labels and contents. But recently, it is found that the hard lock date alert item is only displayed in the short label section of the grid. This commit spans the hard lock date `div`'s `colspan` to 2 to make sure it spans on the whole line. for more info:  task-4586675 Forward-Port-Of: odoo/enterprise#79572
This commit allows the calendar_event_view_form_gantt_booking_inherit form view to display the answers to the questions linked to an appointment. https://github.com/odoo/odoo/pull/196426 Forward-Port-Of: odoo/enterprise#78536
Original PR description
This commit allows the calendar_event_view_form_gantt_booking_inherit form view to display the answers to the questions linked to an appointment. https://github.com/odoo/odoo/pull/196426 Forward-Port-Of: odoo/enterprise#78536
This parameter should have been optional from the beginning. We changed it now because it causes problems when trying to use the TestEdi class with other Tests (Example: AR Website Sales) Forward-Port-Of: odoo/enterprise#79401 Forward-Port-Of: odoo/enterprise#78014
Original PR description
This parameter should have been optional from the beginning. We changed it now because it causes problems when trying to use the TestEdi class with other Tests (Example: AR Website Sales) Forward-Port-Of: odoo/enterprise#79401 Forward-Port-Of: odoo/enterprise#78014
**[FIX] account_online_synchronization: branch company failing to fetch bank's logos.** When a branch company is selected alone with a non admin user, the function `fetch_online_sync_favorite_institutions` fails due to an access error, when trying to access the original companies country code (which is not selected). To reproduce the issue: - Create a branch for a company with a bank journal that hasn't been set up. - Create new internal user with access to the new branch company as we
Original PR description
**[FIX] account_online_synchronization: branch company failing to fetch bank's logos.** When a branch company is selected alone with a non admin user, the function `fetch_online_sync_favorite_institutions` fails due to an access error, when trying to access the original companies country code (which is not selected). To reproduce the issue: - Create a branch for a company with a bank journal that hasn't been set up. - Create new internal user with access to the new branch company as well as the parent (origin of the journal) - Login with the non admin user - Choose soley the newly created branch in company selector - Open invoicing opw-4524368 Forward-Port-Of: odoo/enterprise#79073
This commit fixes an issue with knowledge's members permission computation. If the additional fields given to the method weren't valid fields, the computation would crash and return an error. With this fix we filter the valid additional_fields provided so that we only use those for the computation. task-4562838 Forward-Port-Of: odoo/enterprise#79221
Original PR description
This commit fixes an issue with knowledge's members permission computation. If the additional fields given to the method weren't valid fields, the computation would crash and return an error. With this fix we filter the valid additional_fields provided so that we only use those for the computation. task-4562838 Forward-Port-Of: odoo/enterprise#79221
Task-4577776 Forward-Port-Of: odoo/odoo#197900
Original PR description
Task-4577776 Forward-Port-Of: odoo/odoo#197900