Tuesday, August 16, 2022
14 changes · master
New functionality added to Odoo
This update adds Croatian accounting support in Odoo, including the local chart of accounts, tax reporting, balance sheet, profit and loss reporting, fiscal positions, and translations. It helps companies operating in Croatia use Odoo with country-specific financial reports and accounting setup aligned to local requirements.
Original PR description
- Chart of account - Tax report - Balance sheet - Profit and loss - Fiscal position - Translation
Enhancements to existing features
Spreadsheet pivot filters can now be matched using many-to-many and one-to-many fields, not just single related records. This gives users more flexibility when analyzing connected business data in spreadsheets.
Original PR description
Before this commit, it was only possible to match a pivot with a filter based on a many2one field. Now, it's possible for many2many and one2many fields Task 2946466
Resolved issues and error corrections
Fixed an issue where right-clicking a spreadsheet cell without a pivot formula could cause an error. This improves spreadsheet reliability and prevents interruptions when users open cell context menus.
Original PR description
… crash Since a8eb01024fe6500922c0bb3e89d2fc831f5b2d77, trying to open the context menu of a cell which does not contains at least one pivot formula leads to a traceback. Task-id 2954345
Miscellaneous changes
How to reproduce: - Create a product and set some qty in a package; - For the internal transfer, enable "Move entire packages"; - Create a new internal transfer for the package containing the created product and confirm it; - Open the internal transfer in the Barcode App; - Scan the package -> Its qty. done is updated (0/1 -> 1/1); - Scan it a seconde time -> Its quantity is updated again (1/1 -> 2/1) which is an error (the transfer can't be valided from here). opw-2946401 Forward-
Original PR description
How to reproduce: - Create a product and set some qty in a package; - For the internal transfer, enable "Move entire packages"; - Create a new internal transfer for the package containing the created product and confirm it; - Open the internal transfer in the Barcode App; - Scan the package -> Its qty. done is updated (0/1 -> 1/1); - Scan it a seconde time -> Its quantity is updated again (1/1 -> 2/1) which is an error (the transfer can't be valided from here). opw-2946401 Forward-Port-Of: odoo/enterprise#30289 Forward-Port-Of: odoo/enterprise#30187
The SLA Policy option on product forms has been moved from General Information to the Sales tab. This makes the setting easier for users to find in the area where sales-related product configuration is managed.
Original PR description
… tab This commit just changes the location of the SLA Policy selection in the product form. Previously the SLA Policy selection was under the "General Information" tab but now the selection has been moved under the "Sales" tab. The imporvements in this commit aim at making the placement of the SLA policy setting more intuitive for the users. That, should increase productivity as it will be easier for the user to find the setting if their are looking for it. To implement this change, the product_views.xml file was modified and the new location for the setting was given. Task No: 2919785
Users can now adjust the filter criteria for spreadsheet pivots and lists directly from their properties panel. This makes it easier to refine spreadsheet reports without rebuilding them or needing technical assistance.
Dashboard charts linked to an Odoo menu are now easier to use: instead of a separate external-link button, users can click the whole chart to open the related menu. This streamlines navigation from dashboards and makes chart interactions more intuitive.
Original PR description
Remove button "external link" in charts in dashboard mode, and make the whole figure clickable to redirect to the odoo menu linked to the chart. Odoo task [2947461](https://www.odoo.com/web#id=2947461&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
This fix prevents Sign document fields from displaying the word "false" when placeholders are empty or when users are not in developer mode. It keeps existing placeholder text stable when field types change and updates demo data so sample Sign templates display correctly.
Original PR description
This PR is a followup on https://github.com/odoo/enterprise/pull/27676 where a fix was set in stable to manage the specific case of empty placeholders. However this fix was not stable and made…
This PR is a followup on https://github.com/odoo/enterprise/pull/27676 where a fix was set in stable to manage the specific case of empty placeholders. However this fix was not stable and made pre-existing default placeholder disappear and it was hence revert in https://github.com/odoo/enterprise/pull/28496 on stable versions. This fix in master completes the first fix to treat other issues like the case where the user is not in developer mode, the false that appear in the situation of empty placeholders and a confusion in the js logic where we could not differentiate the name of a sign item that was just created (and has a default value of false) and a sign item that had its placeholder set to false. We also add the placeholders in the demo data. The commits of this PR totally rewrite the first fix commit and can be seen as a minor behavior change (the name field of the sign item always has the value of its placeholder while previously it was only the placeholder when it was not false, this mean that changing the type placeholder won't change the previously existing item default placeholder like it was the case before). BUG1 Steps to reproduce: - Install sign - Put no developer mode on - Set a signature block on a document - Change if from customer to employee Current behavior: The block shows false Expected behavior: The block does not change Explanation: The bug was created after the fix commit 860ace5013d7f5cde1018f5eb1ec4fce1f6b3537 the fix did not take into consideration that the o_sign_name of the block form only appeared when the use is in developer mode (t-if="widget.debug" in xml). https://github.com/odoo/enterprise/blob/da1b8691f8edceac5a7ba794921a24657886618c/sign/static/src/xml/sign_backend.xml#L5-L9 So the name was always false when pulled in the form hide function. To fix that we only pull the name from o_sign_name if we are not in developer mode. BUG2 Steps to reproduce: - Install sign - Create a template and add a sign item - Set an empty placeholder with the developer mode on the sign item and save Expected behavior: The placeholder is empty Current behavior: The placeholder is false Explanation: It was thought in a previous fix https://github.com/odoo/enterprise/commit/860ace5013d7f5cde1018f5eb1ec4fce1f6b3537 that the false value was the expected behavior. But is was just inudced by an empty placeholder in the sign item type that returned the false value. To solve the issue we add || "" after the different places where the name is set so that if the type placeholder is false then the sign item placeholder is an empty string. BUG3 Steps to reproduce: - Create a sign item - Set an empty placeholder with developer mode - Refresh - Click on the sign item you just created Expected behavior: The placeholder is empty Current behavior: The placeholder is the sign item type default placeholder Explanation: The javascript is unabled to make the difference between the name of a sign item that was just created (and has a default value of false) and a sign item that had its placeholder set to false. We solve that in the backend by setting a default value for the sign item name at creation. It's cleaner than the current implementation as the default placeholder is only set once and it makes more sense. opw-2767417 opw-2877149
This update fixes a rare issue where automated checks for spreadsheet links could fail unpredictably. It improves confidence in the Documents Spreadsheet module's test results without changing how users work with spreadsheets.
Original PR description
…sheet Tests using `insertInSpreadsheetAndClickLink()` could (rarely) fail. Replace `await nextTick()` by `await nextRender()` to fix the issue. Odoo task [2946665](https://www.odoo.com/web#id=2946665&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)
This update removes outdated form layout styling from parts of Odoo Enterprise so the interface remains compatible with the newer Bootstrap framework. Users should see no functional change, but these cleanup fixes help prevent visual issues in affected screens and keep the product easier to maintain.
As of now, the address validation button on res partner added by account_avatax is always showing in the form view, even when the setting is disabled. This leads to a button that only display an error unless the setting is enabled. Change this by hiding the button from the view if the setting is not enabled on the company of the partner (or the current company if it does not have one) Task id # 2858113 Forward-Port-Of: odoo/enterprise#29085
Original PR description
As of now, the address validation button on res partner added by account_avatax is always showing in the form view, even when the setting is disabled. This leads to a button that only display an error unless the setting is enabled. Change this by hiding the button from the view if the setting is not enabled on the company of the partner (or the current company if it does not have one) Task id # 2858113 Forward-Port-Of: odoo/enterprise#29085
Forward-Port-Of: odoo/enterprise#30319
Original PR description
Forward-Port-Of: odoo/enterprise#30319
Previous to the commit: If the journal is in manual mode, it unnecessarily validate the existence of CAF files. After the commit The commit skips the requirement of CAF in edi post validation method when the journal is not in online mode. Forward-Port-Of: odoo/enterprise#30325 Forward-Port-Of: odoo/enterprise#27165
Original PR description
Previous to the commit: If the journal is in manual mode, it unnecessarily validate the existence of CAF files. After the commit The commit skips the requirement of CAF in edi post validation method when the journal is not in online mode. Forward-Port-Of: odoo/enterprise#30325 Forward-Port-Of: odoo/enterprise#27165
This PR will make sure that the administrators will always be able to moderate the articles without having explicit "write" access on an article. Currently, the administrator will get access errors when doing the following actions: - When an article inherits its members from its parent and the user does not have "read" access on the parent article, the user gets an access error when opening the share panel of the child article. - When the administrator does not have 'write' access on an arti
Original PR description
This PR will make sure that the administrators will always be able to moderate the articles without having explicit "write" access on an article. Currently, the administrator will get access errors when doing the following actions: - When an article inherits its members from its parent and the user does not have "read" access on the parent article, the user gets an access error when opening the share panel of the child article. - When the administrator does not have 'write' access on an article, the administrator will get an access error when clicking on the 'invite' button (in the invitation wizard) of the share panel. - When the administrator does not have 'write' access on an article, the administrator will get an access error by trying to (1) restore the internal permission of an article, (2) set the internal permission of an article, (3) set the permission of a member, (4) add/remove a member from an article. task-2893614 Forward-Port-Of: odoo/enterprise#29447