Daily updates from Odoo
Thursday, January 11, 2024
23 changes · master
Enhancements to existing features
The GST return period screen structure was reorganized to make it easier to read and maintain. This should help future updates be made more reliably, with little to no direct impact on day-to-day users.
Original PR description
This commit message indicates that the changes made involve restructuring the gst return period view for better readability and ease of maintenance. It's concise and provides a clear understanding of the purpose of the commit.
The room booking calendar now limits the daily Gantt view to meetings scheduled for that specific day. This makes it easier for users to understand room availability without unrelated bookings appearing from nearby dates.
Original PR description
This PR removes `dynamic_range` attribute from the room booking gantt view. which clarifies the daily view by only showing the meetings of that specific day. Task-3623958
A demonstration video has been added to the Knowledge demo article to help users discover and understand the /clipboard command. This improves onboarding by showing what the command does and how to use it in practice.
Original PR description
Currently, users may not know that the /clipboard command exists, may not know what they can do with it and may not know how to use it. To improve the onboarding experience and showcase the /clipboard command, we will integrate a demonstration video in the demo article. After watching this demonstration video, people should better understand the purpose of the /clipboard command and should know how to use it. task-3676051
This update adds automated checks to ensure the help center correctly highlights top forum posts, knowledge articles, and courses. It helps protect the redesigned help center experience from future regressions without changing day-to-day user workflows.
Original PR description
*=forum, knowledge, slides For Odoo 17, the helpdesk center was re-design to include top-item lists for the different help center items: forum posts, knowledge articles, and courses. This commit adds tests in the respective bridge modules to test the compute methods that compute these top items. task-3559939
Resolved issues and error corrections
This fix corrects how payroll holiday dashboard warnings are calculated, preventing an error caused by counting records in the wrong way. Business users should see more reliable dashboard warnings for payroll-related holidays without any change to their workflow.
Original PR description
We apply the len operator on an integer result, which is not correct, we fix that by calling search instead of search_count
The automated report generation test was updated to handle Luxembourg payroll/accounting setups where the related Luxembourg reports module is not installed. This prevents false test failures and helps keep internal validation stable without changing business functionality.
Original PR description
With https://github.com/odoo/odoo/commit/11f73899ef60d56f9e4258d8d9732c8954b288fb, when installing l10n_lu_hr_payroll_account, l10n_lu_reports is not installed (as there is no luxemburgese company). The test test_generate_all_export_files then fails because it expects l10n_lu_reports to be installed if l10n_lu is, and so, some fields don't exist. => To solve, we make the test more robust by ensuring that the fields put on the company do actually exist on the model. Linked to runbot errors 55130, 55131
Miscellaneous changes
The dimension data is not required for shiprocket package to calculate the rate. Calculate the rate based on the total weight of the packages when multiple packages are there. task - 3535687 Forward-Port-Of: odoo/enterprise#48842
Original PR description
The dimension data is not required for shiprocket package to calculate the rate. Calculate the rate based on the total weight of the packages when multiple packages are there. task - 3535687 Forward-Port-Of: odoo/enterprise#48842
2 strings related to creating a new app within studio weren't being correctly translated, so we make them translatable now. Note that the solution before v16 is different (uses getter) because for some reason `<t t-set="variable">Some string</t>` isn't correctly parsed as a string by the props, so an error is thrown while in debug mode. Forward-Port-Of: odoo/enterprise#53967 Forward-Port-Of: odoo/enterprise#53585
Original PR description
2 strings related to creating a new app within studio weren't being correctly translated, so we make them translatable now. Note that the solution before v16 is different (uses getter) because for some reason `<t t-set="variable">Some string</t>` isn't correctly parsed as a string by the props, so an error is thrown while in debug mode. Forward-Port-Of: odoo/enterprise#53967 Forward-Port-Of: odoo/enterprise#53585
This commit fixes a bug where the article items were considered as valid parents when using the **move to** button. These articles should not be considered as such because you could easily lose them when moving them in another hierarchy. We changed the search domain inside the `get_valid_parent_options` function to not include items. task-3627789 Forward-Port-Of: odoo/enterprise#53884 Forward-Port-Of: odoo/enterprise#52307
Original PR description
This commit fixes a bug where the article items were considered as valid parents when using the **move to** button. These articles should not be considered as such because you could easily lose them when moving them in another hierarchy. We changed the search domain inside the `get_valid_parent_options` function to not include items. task-3627789 Forward-Port-Of: odoo/enterprise#53884 Forward-Port-Of: odoo/enterprise#52307
Previously, the sheetName was allowed to be left empty or unchanged after displaying a warning dialog, contrary to the desired behavior. This commit addresses the issue, ensuring that after user confirmation, the sheetName regains focus. Task-3588208 Forward-Port-Of: odoo/enterprise#51654
Original PR description
Previously, the sheetName was allowed to be left empty or unchanged after displaying a warning dialog, contrary to the desired behavior. This commit addresses the issue, ensuring that after user confirmation, the sheetName regains focus. Task-3588208 Forward-Port-Of: odoo/enterprise#51654
Forward-Port-Of: odoo/enterprise#54057
Original PR description
Forward-Port-Of: odoo/enterprise#54057
Steps: - Install subscription app. - Install and set up stripe provider. - Create a subscription and make first payment with stripe. - Now go to portal and click on Manage payment button. - Create new token from Manage my payment button. Issue: - Subscription goes to `Pending Transaction` state and because of that recurring invoice for that subscription stops. Cause: - Transaction with `validation` flow does not reconcile transaction after done via `_reconcile_after_done` and becaus
Original PR description
Steps: - Install subscription app. - Install and set up stripe provider. - Create a subscription and make first payment with stripe. - Now go to portal and click on Manage payment button. - Create new token from Manage my payment button. Issue: - Subscription goes to `Pending Transaction` state and because of that recurring invoice for that subscription stops. Cause: - Transaction with `validation` flow does not reconcile transaction after done via `_reconcile_after_done` and because of that when `validation` transaction create it set subscription to `Pending Transaction` and it stays in it for `validation` PR https://github.com/odoo/odoo/pull/106300 why we do not call `reconcile_after_done` for `validation` transaction. Fix: - Handle `reconcile_after_done` for validation transaction in payment and alter some code/condition in subscription to properly handle all type of transaction. task-3652206 Forward-Port-Of: odoo/enterprise#53374
This commit adds some constraints to the length of the strings sent to Sendcloud. opw-3627831 Forward-Port-Of: odoo/enterprise#53763 Forward-Port-Of: odoo/enterprise#53598
Original PR description
This commit adds some constraints to the length of the strings sent to Sendcloud. opw-3627831 Forward-Port-Of: odoo/enterprise#53763 Forward-Port-Of: odoo/enterprise#53598
This PR solves an issue about the dropdown toggle from the topbar navigation not being highlighted on `:focus` state. This comes from a color issue, the `background-color` of the toggle being the same as the navbar one in dark mode. To solve this issue, we redefine the variable in dark mode, and set it to `$o-gray-300`. task-3607749 Forward-Port-Of: odoo/enterprise#51285
Original PR description
This PR solves an issue about the dropdown toggle from the topbar navigation not being highlighted on `:focus` state. This comes from a color issue, the `background-color` of the toggle being the same as the navbar one in dark mode. To solve this issue, we redefine the variable in dark mode, and set it to `$o-gray-300`. task-3607749 Forward-Port-Of: odoo/enterprise#51285
Steps to reproduce: - Install Accounting and Inventory - Activate "Units of Measure" in Inventory settings - Activate "Intrastat" in Accounting settings - Create a product: (e.g. Product X) * Unit of Measure: Dozens * Purchase UoM: Dozens * Cost: [any] * Commodity Code: [any] (e.g. 01012100 Pure-bred breeding horses) * Supplementary Units: 0.33 - Create a vendor bill: * Intrastat Country: [any] * Invoice Lines: - Product: Product X - Quantity: 126 - Confirm v
Original PR description
Steps to reproduce:
- Install Accounting and Inventory
- Activate "Units of Measure" in Inventory settings
- Activate "Intrastat" in Accounting settings
- Create a product: (e.g. Product X)
* Unit of Measure: Dozens
* Purchase UoM: Dozens
* Cost: [any]
* Commodity Code: [any] (e.g. 01012100 Pure-bred breeding horses)
* Supplementary Units: 0.33
- Create a vendor bill:
* Intrastat Country: [any]
* Invoice Lines:
- Product: Product X
- Quantity: 126
- Confirm vendor bill
- Go to "Accounting / Reporting / Audit Reports / Intrastat Report"
- Filter on the vendor bill period
=> The value of "Supplementary Units" is displayed with a lot of decimal digits (i.e. 498.96000000000004).
Cause:
Floating point issue during the computation of the field.
Solution:
Round "Supplementary Units" field to the decimal accuracy configured for "Product Unit of Measure".
opw-3464654
Forward-Port-Of: odoo/enterprise#52264### Steps to reproduce - install the following modules: - Accounting - Studio - Saudi Arabia - Accounting (l10n_sa) - Go to Settings > Users & Companies > Companies and create a New Company (named S**A Company** for example) with Saudi Arabia as the country in the address - Switch to the new **SA Company** - Go to Settings > Accounting - Choose Saudi Arabia package as the Fiscal Localization package - Go to Accounting and click on the studio icon (the one left of the user
Original PR description
### Steps to reproduce - install the following modules: - Accounting - Studio - Saudi Arabia - Accounting (l10n_sa) - Go to Settings > Users & Companies > Companies and create a New Company (named…
### Steps to reproduce
- install the following modules:
- Accounting
- Studio
- Saudi Arabia - Accounting (l10n_sa)
- Go to Settings > Users & Companies > Companies and create a New Company (named S**A Company** for example) with Saudi Arabia as the country in the address
- Switch to the new **SA Company**
- Go to Settings > Accounting
- Choose Saudi Arabia package as the Fiscal Localization package
- Go to Accounting and click on the studio icon (the one left of the user profile avatar)
- Click on reports
- Clear the filters
- Click on Invoices
- Click on the **Company tagline** box
- In the select box shown, choose `elif: o._get_name_invoice_report() == '|10n_gccarabic_english_invoice'`
- U can notice how the template is not rendered correctly
### Investigation:
- the major issue was the `flex-direction: column;` that caused the table header to be viewed as blocks
https://github.com/odoo/enterprise/blob/e892bc8f022ed3962de06a61c1be181c89cdc831/web_studio/static/src/client_action/report_editor/report_iframe.scss#L170C1-L187C2
- Some xml tags / classes needed to be refined to enhance the layout
opw-3544938
Forward-Port-Of: odoo/enterprise#51711Before this PR when we log in as internal user it is giving access error when trying to open url of the task. So in this PR we have fixed the issue by adding sudo task-3430762 Forward-Port-Of: odoo/enterprise#53911 Forward-Port-Of: odoo/enterprise#44530
Original PR description
Before this PR when we log in as internal user it is giving access error when trying to open url of the task. So in this PR we have fixed the issue by adding sudo task-3430762 Forward-Port-Of: odoo/enterprise#53911 Forward-Port-Of: odoo/enterprise#44530
Before this commit: When a user creates a new spreadsheet in all workspace, the trash workspace was included in the selection. After this commit: The trash workspace is no longer available in the selection when creating a new spreadsheet in all workspace. Task-3584275 Forward-Port-Of: odoo/enterprise#50347
Original PR description
Before this commit: When a user creates a new spreadsheet in all workspace, the trash workspace was included in the selection. After this commit: The trash workspace is no longer available in the selection when creating a new spreadsheet in all workspace. Task-3584275 Forward-Port-Of: odoo/enterprise#50347
https://eservices.minfin.fgov.be/myminfin-web/pages/public/fisconet/document/9e9a6b60-c329-4132-9d57-a4fd33aafe0e Forward-Port-Of: odoo/enterprise#53877 Forward-Port-Of: odoo/enterprise#53548
Original PR description
https://eservices.minfin.fgov.be/myminfin-web/pages/public/fisconet/document/9e9a6b60-c329-4132-9d57-a4fd33aafe0e Forward-Port-Of: odoo/enterprise#53877 Forward-Port-Of: odoo/enterprise#53548
Before this commit, in the Operations Types Barcode Apps configuration, if the setting for Destination Location or Put in Pack was set on "After group of Products", once in the app, if the user scans multiple products then scan a destination, the destination is actually applied only to the last scanned product. For the put in pack, all the scanned product were placed in the package, except when an existing package is scanned (in this case, like for the destination, only the last scanned produc
Original PR description
Before this commit, in the Operations Types Barcode Apps configuration, if the setting for Destination Location or Put in Pack was set on "After group of Products", once in the app, if the user scans…
Before this commit, in the Operations Types Barcode Apps configuration, if the setting for Destination Location or Put in Pack was set on "After group of Products", once in the app, if the user scans multiple products then scan a destination, the destination is actually applied only to the last scanned product. For the put in pack, all the scanned product were placed in the package, except when an existing package is scanned (in this case, like for the destination, only the last scanned product was concerned.) This worked like that because in fact, this setting's option reflected the old optional setting and should work like before the creation of those settings. But the label, "After group of Product", was misleading and it could be verify interesting to make those settings work like the label said and applied the destination and the package after a group of scanned product. This commit do that. But this change implies an issue: what should happen if you scan partially a reserved line then scan a destination or a package ? Should all the quantity be moved there ? To avoid this issue, we split the reservation before to assign the package or destination on an uncompleted reserved line. task-3599397 Forward-Port-Of: odoo/enterprise#51603
* Show the current value of the cell in the edit popover * Replace the input by a textarea when the cell figure_type is 'string'. It gives more space for the user to write. Forward-Port-Of: odoo/enterprise#52623
Original PR description
* Show the current value of the cell in the edit popover * Replace the input by a textarea when the cell figure_type is 'string'. It gives more space for the user to write. Forward-Port-Of: odoo/enterprise#52623
Steps to reproduce the bug: - Create a storable product “P1”: - Tracking: SN - Update the qty: 1 unit, “SN1” - Create a SO with and validate it - Go to the delivery and validate it - Create a return and validate - Create a return of return Problem: error message: RecursionError: maximum recursion depth exceeded while calling a Python object The `_get_origin_moves` and `_get_destination_moves` functions add the list of origin or destination moves, but the functions themselves are ca
Original PR description
Steps to reproduce the bug: - Create a storable product “P1”: - Tracking: SN - Update the qty: 1 unit, “SN1” - Create a SO with and validate it - Go to the delivery and validate it - Create a return and validate - Create a return of return Problem: error message: RecursionError: maximum recursion depth exceeded while calling a Python object The `_get_origin_moves` and `_get_destination_moves` functions add the list of origin or destination moves, but the functions themselves are called with that list, creating an infinite loop. opw-3659818 Forward-Port-Of: odoo/enterprise#53695
Forward-Port-Of: odoo/enterprise#53669 Forward-Port-Of: odoo/enterprise#53627
Original PR description
Forward-Port-Of: odoo/enterprise#53669 Forward-Port-Of: odoo/enterprise#53627