Wednesday, September 11, 2024
32 changes
11 changes
Resolved issues and error corrections
Kitchen receipts in Point of Sale now handle very long product names without text overlapping other lines. This keeps order preparation tickets readable for restaurant staff and reduces confusion in the kitchen.
Original PR description
When printing order changes that contains a product with a really long name, the product name would overlap on the kitchen receipt. Steps to reproduce: ------------------- * Modify the name of a product so that it is really long * Setup a kitchen printer on a PoS restaurant * Add some product on an order and send the order in preparation > Observation: The kitchen receipt has overlapping lines Why the fix: ------------ We make sure to hide the overflowing text so that it is not overlapping on other lines. opw-4136775 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
In this commit: =================== If the customer is not loaded, you can find them in the backend by barcode now. Task - 4074907 Forward-Port-Of: odoo/odoo#177576
Original PR description
In this commit: =================== If the customer is not loaded, you can find them in the backend by barcode now. Task - 4074907 Forward-Port-Of: odoo/odoo#177576
21 changes
Enhancements to existing features
Kanban card layouts in Timesheets, Enterprise web, and Studio were simplified to use newer standard building blocks. This makes the views easier to maintain and helps keep the user interface consistent without changing core business workflows.
Original PR description
* = [web_enterprise, web_studio] In this commit we have simplified the kanban archs for the timesheet_grid, web_enterprise and web_studio modules. The goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used `kanban-box`, but now we are using `kanban-card` instead. - Deprecated `oe_kanban_global_click` and `oe_kanban_global_click_edit`. - More use of `<field/>` tags - Removed the `oe_kanban_colorpicker` class and replaced it with the `kanban_color_picker` widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - `kanban_image` from rendering context, is deprecated so we use `<field name=... widget=image/>` instead Task-3992107
### Steps to reproduce issue: 1. Create new Expense 2. Give a positive Total Amount, add a Tax and Save 3. Set Total Amount to 0 4. Tax Amount did not nullify 5. In the List view, Total Amount still has the previous value ### Explanation: In `_convert_to_tax_base_line_dict`, `price_unit` is only passed if it has a strictly positive value, otherwise `total_amount_company` is used instead. Since `total_amount_company` is computed using this method, it can never be reset to 0. https:
Original PR description
### Steps to reproduce issue: 1. Create new Expense 2. Give a positive Total Amount, add a Tax and Save 3. Set Total Amount to 0 4. Tax Amount did not nullify 5. In the List view, Total Amount still has the previous value ### Explanation: In `_convert_to_tax_base_line_dict`, `price_unit` is only passed if it has a strictly positive value, otherwise `total_amount_company` is used instead. Since `total_amount_company` is computed using this method, it can never be reset to 0. https://github.com/odoo/odoo/blob/72b84435d69d098d615284d84ef136e8bcd2aaa0/addons/hr_expense/models/hr_expense.py#L226-L232 ### Suggested Fix: The fallback to `total_amount_company` is unnecessary. For `quantity`, the fallback to 1 should only be observed if the quantity is not set. Correcting `_inverse_total_amount` to avoid division by 0. opw-4049853 Forward-Port-Of: odoo/odoo#179099 Forward-Port-Of: odoo/odoo#174484
Before this commit, entering a payment amount with cash rounding higher than one (e.g., 10) incorrectly triggered an error popup every time. opw-4124332 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#178886 Forward-Port-Of: odoo/odoo#177547
Original PR description
Before this commit, entering a payment amount with cash rounding higher than one (e.g., 10) incorrectly triggered an error popup every time. opw-4124332 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#178886 Forward-Port-Of: odoo/odoo#177547
Using the name field in the domain for a discount product would cause the search to break because name was not being loaded into the Javascript through this function _loader_params_product_product. Changed the types of errors that are thrown instead being shown a notification popup in order to avoid the clunky Javascript error in the case of a typeerror from not having the field loaded. opw-4027900 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Original PR description
Using the name field in the domain for a discount product would cause the search to break because name was not being loaded into the Javascript through this function _loader_params_product_product. Changed the types of errors that are thrown instead being shown a notification popup in order to avoid the clunky Javascript error in the case of a typeerror from not having the field loaded. opw-4027900 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#172372
Some keys were named using `-` to separate words some place and `_` some other place. Forward-Port-Of: odoo/odoo#179772
Original PR description
Some keys were named using `-` to separate words some place and `_` some other place. Forward-Port-Of: odoo/odoo#179772
This commit adds the possibility to disable the month or quarter granularity (or both) for fixedPeriod date filters. Task: [3887844](https://www.odoo.com/web#id=3887844&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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
Original PR description
This commit adds the possibility to disable the month or quarter granularity (or both) for fixedPeriod date filters. Task: [3887844](https://www.odoo.com/web#id=3887844&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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#178956 Forward-Port-Of: odoo/odoo#169922
The test "test_account_move_payment_method" was failing in community only because the payment_state is paid if only l10n_it is installed but is in_payment if the enterprise module is installed. We decided to totally remove the if statement on the payment_state. The matching numbers are enough. Also adding some early returns in the compute to make sure we don't do the search on account.move.line for nothing or compute the document type for non italian companies. no task-id --
Original PR description
The test "test_account_move_payment_method" was failing in community only because the payment_state is paid if only l10n_it is installed but is in_payment if the enterprise module is installed. We decided to totally remove the if statement on the payment_state. The matching numbers are enough. Also adding some early returns in the compute to make sure we don't do the search on account.move.line for nothing or compute the document type for non italian companies. no task-id --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#178235
It happens often enough that whenever someone wants to install The US Accounting localization they have a hard time finding it because they do not know that the "Generic Chart Template" is for the US. This task will rename the template so that it's more clear for users. task: 4146856 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179133
Original PR description
It happens often enough that whenever someone wants to install The US Accounting localization they have a hard time finding it because they do not know that the "Generic Chart Template" is for the US. This task will rename the template so that it's more clear for users. task: 4146856 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179133
Issue ---- When work orders are computed, the compute function may delete some of the previous work orders. However, it doesn't take into account these deleted work orders when choosing whether to update or create a work order. So it ends up issuing an update command after a delete command for the same order. This happens during splitting and causes work orders to disappear. Steps ----- - Open Manufacturing -> Create a storable product and a BoM for this product. - Create a prod
Original PR description
Issue ---- When work orders are computed, the compute function may delete some of the previous work orders. However, it doesn't take into account these deleted work orders when choosing whether to…
Issue ---- When work orders are computed, the compute function may delete some of the previous work orders. However, it doesn't take into account these deleted work orders when choosing whether to update or create a work order. So it ends up issuing an update command after a delete command for the same order. This happens during splitting and causes work orders to disappear. Steps ----- - Open Manufacturing -> Create a storable product and a BoM for this product. - Create a product as part of the BoM. - For the latter product, create another BoM that is a kit. - Create an operation in the BoM of the kit. - Create a manufacturing order for the storable product (first created product). - Set a quantity larger than 1, say 10, and manually save the MO (without confirming it). - Split the MO into same quantity (e.g. 10), and after confirming the split the following traceback is triggered: `remaining_qty = initial_workorder_remaining_qty[index % workorders_len] ZeroDivisionError: integer division or modulo by zero` opw-3994583 Forward-Port-Of: odoo/odoo#171493
### Current Behavior: When scanning a barcode like attached, ascii 29 (FNC1) will be added to the beginning of the final code. ### Expected Behavior: FNC1 should be removed from the final code. ### Steps to Reproduce 1. With barcode installed, set the barcode nomenclature in settings to "Default GS1 Nomenclature" 2. Attempt to scan this barcode  3. If you debug [here](https://github.com/
Original PR description
### Current Behavior: When scanning a barcode like attached, ascii 29 (FNC1) will be added to the beginning of the final code. ### Expected Behavior: FNC1 should be removed from the final code. ###…
### Current Behavior: When scanning a barcode like attached, ascii 29 (FNC1) will be added to the beginning of the final code. ### Expected Behavior: FNC1 should be removed from the final code. ### Steps to Reproduce 1. With barcode installed, set the barcode nomenclature in settings to "Default GS1 Nomenclature" 2. Attempt to scan this barcode  3. If you debug [here](https://github.com/odoo-dev/odoo/blob/b387345f557adace35767ec2ca7ada271cca8423/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L101), you will find that `barcode` starts with ascii 29, but it isn't removed. ### Details This commit adds ascii code 29 (FNC1) to the list of strings to be escaped from in gs1 decomposition. In PR #163404, logic was added to escape barcode scan results that start with FNC1. This is only specifically checking ']C1', but it is possible for the literal ascii code 29 to be present in the beginning of the string as well. This should also be escaped. You can see that ascii 29 is added in `zxing-library.js` [here](https://github.com/odoo-dev/odoo/blob/b387345f557adace35767ec2ca7ada271cca8423/addons/web/static/lib/zxing-library/zxing-library.js#L12308) in this case. It also could potentially be added in several other places such as [here](https://github.com/odoo-dev/odoo/blob/b387345f557adace35767ec2ca7ada271cca8423/addons/web/static/lib/zxing-library/zxing-library.js#L6932) opw-3965925 Forward-Port-Of: odoo/odoo#177958
Onboarding tours across several business apps are now registered in the database so they can be reliably discovered and launched. This keeps guided setup experiences working after a platform change that moved tour registration into stored configuration.
Original PR description
After the change in https://github.com/odoo/odoo/pull/177564 The onboarding tours have to be register in the database. TASK-ID: 4070659
Project and field service kanban cards were updated to use newer standard building blocks and clearer layout definitions. This makes the screens easier to maintain while preserving the same business workflows for users.
Original PR description
*industry_fsm, industry_fsm_report, industry_fsm_sale, project_enterprise, timesheet_grid In this commit we have simplified the kanban arch for the project and related module. The goal is to simplify them, make them easier to read, and use bootstrap utility classnames. - Previously, we used `kanban-box`, but now we are using `kanban-card` instead. - Deprecated `oe_kanban_global_click` and `oe_kanban_global_click_edit`. - More use of `<field/>` tags - Removed the `oe_kanban_colorpicker` class and replaced it with the `kanban_color_picker` widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - `kanban_image` from rendering context, is deprecated so we use `<field name=... widget=image/>` instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color=color_field_name on root node Task-3992107
The stock barcode screens have been simplified to use newer standard layout components and styling. This makes the interface easier to maintain and helps keep barcode picking and batch picking views consistent with current Odoo conventions.
Original PR description
In this commit we have simplified the kanban arch for the stock and their related modules.the goal is to simplify them, make them easier to read and use bootstrap utility classnames. - Previously, we used kanban-box, but now we are using kanban-card instead. - Deprecated oe_kanban_global_click and oe_kanban_global_click_edit. - More use of <field/> tags - Removed the oe_kanban_colorpicker class and replaced it with the kanban_color_picker widget. - Changed type='edit' to type='open' to open records. since version 16, records always open in edit mode by default. - kanban_image from rendering context, is deprecated so we use <field name="..." widget="image"/> instead - kanban_color, kanban_getcolor and kanban_getcolorname are deprecated use new attribute highlight_color="color_field_name" on root node Task-3992107
Resolved issues and error corrections
The Appointments schedule menu is now hidden from users who do not have permission to access it. This prevents confusing access error messages when staff try to open resource or staff booking schedules they are not allowed to view.
Original PR description
**Steps to reproduce:** Log in as Demo. Go to Appointments > Schedule > Resource bookings / Staff bookings. Both menus result in an Access Rights Error. After commit https://github.com/odoo/enterprise/commit/f406f3b7ed34ac53bacdaa44ca359a2dbbd152ba, the schedule menu is also visible for those users who don't have access to it. **After this PR:** Hide the schedule menu for those users who don't have access to it. Task-4172809
A spelling mistake was corrected in the UrbanPiper restaurant integration information. This is a minor cleanup that improves presentation and avoids confusion in module details.
The guided timesheet walkthrough no longer gets stuck when users click a timesheet cell to enter hours. This keeps onboarding and training flows smooth by ensuring the tour recognizes the click even when an overlay appears on hover.
Original PR description
Steps to reproduce: - start timesheets tour - when reaching step "Click on the cell to set the number of hours you spent on this project.", and clicking on the cell, tour stay at the same step. Source: - when hovering the cell, a new html element came to superpose above the trigger. so the click is done on the new element and not the trigger. Fix: - The fix was done in task 4147246, this commit just adapted the trigger with an additional alternative trigger task-4141027
New tables added in Studio report editing now follow the report's existing external layout styling. This keeps reports visually consistent and avoids manual formatting corrections after inserting tables.
Original PR description
Before this commit, when inserting a new table in the report, its style was off because of the specific styles set by the external layout After this commit, the styles fit the external layout's task-4166611
Automatic bank reconciliation now prefers an active customer or vendor when matching a bank statement line by account number. This helps avoid assigning inactive contacts during reconciliation while still allowing reconciliation when there is only one possible match.
Original PR description
…sible Context: When doing automatic reconciliation, statement lines without partner but with account_number set are using the method `_retrieve_partner` to find a partner which would have a bank account with the same account_number. Problem: The res.partner.bank could be active and the partner inactive, which would result in selecting an inactive partner for the reconciliation. This commit improve on that behavior by trying to assign an active partner if we happen to have one with the same bank account and if it is not possible, we still leave the inactive partner but we disable the "auto reconcile" part of the reconciliation. Task: 3975338
Code cleanup and technical improvements
This update changes how test files are created so they work consistently across more web browsers. It reduces the risk of browser-specific test failures in Documents, Payroll, Mail, and WhatsApp-related areas without changing customer-facing features.
Original PR description
*test_l10n_be_hr_payroll_account, test_mail_enterprise, whatsapp Purpose of this commit: `createFile` used the File System API to create test files in the browser's temporary file system. However, since not all browsers support this API, it has been replaced with the new File(...) constructor, which is supported by all browsers. This change makes the tests more compatible across different browsers. community: https://github.com/odoo/odoo/pull/179600 task-4161755
Miscellaneous changes
Before this commit, in studio, the editorMenu was not updated when clicking on a different tab (views, automations etc...) After this commit, the menu is updated. Forward-Port-Of: odoo/enterprise#69809 Forward-Port-Of: odoo/enterprise#69795
Original PR description
Before this commit, in studio, the editorMenu was not updated when clicking on a different tab (views, automations etc...) After this commit, the menu is updated. Forward-Port-Of: odoo/enterprise#69809 Forward-Port-Of: odoo/enterprise#69795
When exporting GL in datev format, the receivable/payable accounts were not well formatted. Steps: - duplicate the Receivable Account (A) - create a customer C with receivable set as A - create and confirm an invoice for C - go to GL and export datev file -> column konto is account code of A, it should be 1000000 + C.id, according to datev (starting by 1 for customers and 7 for Vendors) Before this commit, we were making the distinction between the customers that had the "original" rece
Original PR description
When exporting GL in datev format, the receivable/payable accounts were not well formatted. Steps: - duplicate the Receivable Account (A) - create a customer C with receivable set as A - create and confirm an invoice for C - go to GL and export datev file -> column konto is account code of A, it should be 1000000 + C.id, according to datev (starting by 1 for customers and 7 for Vendors) Before this commit, we were making the distinction between the customers that had the "original" receivable account and the others, and we were displaying the account code in the second case. It should be the datev format in any case. opw-4117993 Forward-Port-Of: odoo/enterprise#69573
Add tests for the community side changes in https://github.com/odoo/odoo/pull/167235, as these changes mostly impact inter-company transaction flows. task-3853055 Forward-Port-Of: odoo/enterprise#69715 Forward-Port-Of: odoo/enterprise#64078
Original PR description
Add tests for the community side changes in https://github.com/odoo/odoo/pull/167235, as these changes mostly impact inter-company transaction flows. task-3853055 Forward-Port-Of: odoo/enterprise#69715 Forward-Port-Of: odoo/enterprise#64078
no task Forward-Port-Of: odoo/enterprise#69643
Original PR description
no task Forward-Port-Of: odoo/enterprise#69643
This commit adds the missing neutralization necessary for the l10n_uy_edi module introduced in [1] The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of the production database. This is ma
Original PR description
This commit adds the missing neutralization necessary for the l10n_uy_edi module introduced in [1] The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of the production database. This is mainly useful to allow safe support investigation on database duplicates. [1] https://github.com/odoo/enterprise/pull/51266 Forward-Port-Of: odoo/enterprise#69692 Forward-Port-Of: odoo/enterprise#69555
…orders The cron _cron_confirm_purchase_orders run only once a week, month and do nothing the rest of the week month The cron may timeout and get delay to it's next execution date before all the po to process are done This leave some draft pos that won't be handle before next month/week and generate unacceptable delay. The cron should notify its progress in order to be able to run as much as needed. In order to have a consistent progress notified, this commit first fech all the pos t
Original PR description
…orders The cron _cron_confirm_purchase_orders run only once a week, month and do nothing the rest of the week month The cron may timeout and get delay to it's next execution date before all the po to process are done This leave some draft pos that won't be handle before next month/week and generate unacceptable delay. The cron should notify its progress in order to be able to run as much as needed. In order to have a consistent progress notified, this commit first fech all the pos to process and then process them one by one. Forward-Port-Of: odoo/enterprise#69598
eBay recently changed the URL they send in the viewitemURL. We found 3 different ways they send it, but there might be more. And the new ones can only be matched to the product template, not variant. We shouldn't have relied on this URL to match products in the beginning, but we can't refactor this flow in stable, instead, we fallback on the name of the variant, as it was created from eBay. opw-3934127 Forward-Port-Of: odoo/enterprise#69152
Original PR description
eBay recently changed the URL they send in the viewitemURL. We found 3 different ways they send it, but there might be more. And the new ones can only be matched to the product template, not variant. We shouldn't have relied on this URL to match products in the beginning, but we can't refactor this flow in stable, instead, we fallback on the name of the variant, as it was created from eBay. opw-3934127 Forward-Port-Of: odoo/enterprise#69152
commit [1] introduce alias to handle scale up game but scale up ask to create a database without demo. So we move the alias to data. It's far from optimal but it's the cleaner temporary solution [1] commit cfe4829be00c77935555d506d86f0f14618fd21f Forward-Port-Of: odoo/enterprise#69773
Original PR description
commit [1] introduce alias to handle scale up game but scale up ask to create a database without demo. So we move the alias to data. It's far from optimal but it's the cleaner temporary solution [1] commit cfe4829be00c77935555d506d86f0f14618fd21f Forward-Port-Of: odoo/enterprise#69773
Currently, an exception is generated when the user tries to open the "Cash Flow Statement" report. Steps to produce an error: - install 'Accounting Reports' - Open Accounting > Configuration > Accounting > Journals - Now delete all journals except "Miscellaneous Operations" - change type of "Miscellaneous Operations" to sales > sale - Click Reporting > click "Cash Flow Statement" >>> exception occurs Stack Trace: ``` SyntaxError: syntax error at or near ")" LINE 28: ...
Original PR description
Currently, an exception is generated when the user tries to open the "Cash Flow Statement" report. Steps to produce an error: - install 'Accounting Reports' - Open Accounting > Configuration >…
Currently, an exception is generated when the user tries to open the "Cash Flow Statement" report.
Steps to produce an error:
- install 'Accounting Reports'
- Open Accounting > Configuration > Accounting > Journals
- Now delete all journals except "Miscellaneous Operations"
- change type of "Miscellaneous Operations" to sales > sale
- Click Reporting > click "Cash Flow Statement" >>> exception occurs
Stack Trace:
```
SyntaxError: syntax error at or near ")"
LINE 28: ... AND account_move_line.account_id NOT IN ((), ())
^
File "odoo/http.py", line 2373, in __call__
response = request._serve_db()
File "odoo/http.py", line 1903, in _serve_db
return self._transactioning(
File "odoo/http.py", line 1966, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 134, in retrying
result = func()
File "odoo/http.py", line 1933, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2177, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 223, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 754, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "addons/web/controllers/dataset.py", line 35, in call_kw
return call_kw(request.env[model], method, args, kwargs)
File "odoo/api.py", line 459, in call_kw
result = getattr(recs, name)(*args, **kwargs)
File "home/odoo/src/enterprise/saas-17.4/account_reports/models/account_report.py", line 4872, in get_report_information
'lines': self._get_lines(options, all_column_groups_expression_totals=all_column_groups_expression_totals, warnings=warnings),
File "home/odoo/src/enterprise/saas-17.4/account_reports/models/account_report.py", line 2275, in _get_lines
dynamic_lines = self._get_dynamic_lines(options, all_column_groups_expression_totals, warnings=warnings)
File "home/odoo/src/enterprise/saas-17.4/account_reports/models/account_report.py", line 2705, in _get_dynamic_lines
rslt = self.env[self.custom_handler_model_name]._dynamic_lines_generator(self, options, all_column_groups_expression_totals, warnings=warnings)
File "home/odoo/src/enterprise/saas-17.4/account_reports/models/account_cash_flow_report.py", line 16, in _dynamic_lines_generator
report_data = self._get_report_data(report, options, layout_data)
File "home/odoo/src/enterprise/saas-17.4/account_reports/models/account_cash_flow_report.py", line 57, in _get_report_data
for aml_groupby_account in self._get_liquidity_moves(report, options, currency_table_query, payment_account_ids, cashflow_tag_ids):
File "home/odoo/src/enterprise/saas-17.4/account_reports/models/account_cash_flow_report.py", line 365, in _get_liquidity_moves
self._cr.execute(SQL(' UNION ALL ').join(queries))
File "odoo/sql_db.py", line 347, in execute
res = self._obj.execute(query, params)
```
This is because at the time of query building for getting liquidity moves, it gets an empty tuple from line [1] as we do not have any journals with the type 'bank', 'cash', or 'general'.
This commit will fix the above issue by returning empty report_data when payment_account_ids is empty.
[1] - https://github.com/odoo/enterprise/blob/8fa01948610809d191b75260772782e25ea3a737/account_reports/models/account_cash_flow_report.py#L195
sentry-5555757610
Forward-Port-Of: odoo/enterprise#67928This commit fix a design issue in the hr_payroll where the "Availability in Structure" field was incorrectly positioned among other input types. task-4050183 Forward-Port-Of: odoo/enterprise#69761 Forward-Port-Of: odoo/enterprise#67532
Original PR description
This commit fix a design issue in the hr_payroll where the "Availability in Structure" field was incorrectly positioned among other input types. task-4050183 Forward-Port-Of: odoo/enterprise#69761 Forward-Port-Of: odoo/enterprise#67532
Since #64854 view_model_tree inherited an action on click that was meant only for a specific view this action has been moved to a primary inherited view. Related to task-id: 3861100 backport of odoo/enterprise#68107 Forward-Port-Of: odoo/enterprise#69751
Original PR description
Since #64854 view_model_tree inherited an action on click that was meant only for a specific view this action has been moved to a primary inherited view. Related to task-id: 3861100 backport of odoo/enterprise#68107 Forward-Port-Of: odoo/enterprise#69751