Daily updates from Odoo
Navigate
Branch
Thursday, September 29, 2022
25 changes
New functionality added to Odoo
Adds Estonian accounting localization reports, including VAT export, EC sales reporting, balance sheet, and income statement. This helps businesses operating in Estonia meet local reporting requirements directly in Odoo.
Original PR description
Task-ID: [2985062](https://www.odoo.com/web#id=2985062&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form) Add the Estonian localization for accounting: - XML export for VAT Report - IC Supply Report (EC Sales) - Form VD + XML export - Balance Sheet - Income Statement (P/L) Related Community PR: https://github.com/odoo/odoo/pull/101636
Enhancements to existing features
When an employee contract is cancelled, any related signature requests are cancelled automatically. This keeps contract records, pending signatures, and follow-up activities aligned so teams do not chase documents for cancelled contracts.
Original PR description
When a contract is cancelled, its linked sign requests should be cancelled as well and the activities linked to those requests closed. task-2984663
Subscription reports now apply currency conversion so figures are shown consistently across different currencies. This improves accuracy for businesses comparing subscription performance across companies, countries, or customer currencies.
Original PR description
Apply currency conversion on reports. Inspired by : odoo/odoo#83550 task-id : 2286717
Code cleanup and technical improvements
The Planning form view has been converted to a newer interface framework and corrected so it is ready for future use. There is no immediate change for users because the current Gantt-based flow still uses the existing legacy form.
Original PR description
This commit converts the form view to wowl. Also, it corrects the view. Note : The form view is called from gantt, which is still in legacy. As a consequence, this commit just aims to make the converted view available when it will be needed, but the legacy view remains in use. task-2922976
Miscellaneous changes
Reproduction steps: - Install timesheet_grid - Go to the timesheet tree view - Merge the timesheets Forward-Port-Of: odoo/enterprise#31892
Original PR description
Reproduction steps: - Install timesheet_grid - Go to the timesheet tree view - Merge the timesheets Forward-Port-Of: odoo/enterprise#31892
Tests adaptations will come in a following PR, but the current focus is set on owl conversion. Forward-Port-Of: odoo/enterprise#31958
Original PR description
Tests adaptations will come in a following PR, but the current focus is set on owl conversion. Forward-Port-Of: odoo/enterprise#31958
This problem occurs because we previously change the default line-height to 1.0 https://github.com/odoo/enterprise/commit/6317774e30066cadc789ad239e19549a0445fc03 so to solve this problem we remove some css weird rules Steps to reproduce: 1. Go to Sale -> To Invoice -> Order To invoice 2. Open the order number "S00061" 3. Click on the customer "YourCompany, Joel Willis" 4. Lock at the chatter, the rendered mail as some weird scrollbar => bug Forward-Port-Of: odoo/enterprise#31904
Original PR description
This problem occurs because we previously change the default line-height to 1.0 https://github.com/odoo/enterprise/commit/6317774e30066cadc789ad239e19549a0445fc03 so to solve this problem we remove some css weird rules Steps to reproduce: 1. Go to Sale -> To Invoice -> Order To invoice 2. Open the order number "S00061" 3. Click on the customer "YourCompany, Joel Willis" 4. Lock at the chatter, the rendered mail as some weird scrollbar => bug Forward-Port-Of: odoo/enterprise#31904
The registry is mostly used by kanban, list and form views. Adding grid widgets to that registry is useless, as grid directly imports them, thus bypassing the registry. Forward-Port-Of: odoo/enterprise#31891
Original PR description
The registry is mostly used by kanban, list and form views. Adding grid widgets to that registry is useless, as grid directly imports them, thus bypassing the registry. Forward-Port-Of: odoo/enterprise#31891
Converts hr_payroll and hr_payroll_holidays calendar views to owl. task-2992657 Forward-Port-Of: odoo/enterprise#31813
Original PR description
Converts hr_payroll and hr_payroll_holidays calendar views to owl. task-2992657 Forward-Port-Of: odoo/enterprise#31813
- Fixes the scrolling (scrollbar did not appear on small screens) - Makes the UI more responsive, wrapping rows on smaller screens Forward-Port-Of: odoo/enterprise#31734
Original PR description
- Fixes the scrolling (scrollbar did not appear on small screens) - Makes the UI more responsive, wrapping rows on smaller screens Forward-Port-Of: odoo/enterprise#31734
Steps to reproduce: 1- Install delivery_fedex, sales 2- make a sales Order with a product with HS code with dots in it 3- add Fedex International shipping 4- You get an error that the HS code is wrong Bug: although the HS codes are displayed with dots in the search engine of Fedex, the API expects them without the dots Fix: strip the dots from the harmonized code before sending the request OPW-2906511 Forward-Port-Of: odoo/enterprise#31800 Forward-Port-Of: odoo/enterprise#29
Original PR description
Steps to reproduce: 1- Install delivery_fedex, sales 2- make a sales Order with a product with HS code with dots in it 3- add Fedex International shipping 4- You get an error that the HS code is wrong Bug: although the HS codes are displayed with dots in the search engine of Fedex, the API expects them without the dots Fix: strip the dots from the harmonized code before sending the request OPW-2906511 Forward-Port-Of: odoo/enterprise#31800 Forward-Port-Of: odoo/enterprise#29440
When going through _predict_product() due to an onchange recompute, only lines with product_id are taken into account even if there are more lines without product_id that could fit. This fix ensures that lines without product_id are taken into account when trying to predict a product. Followup on #30906 opw-2986213 Forward-Port-Of: odoo/enterprise#31976 Forward-Port-Of: odoo/enterprise#31922
Original PR description
When going through _predict_product() due to an onchange recompute, only lines with product_id are taken into account even if there are more lines without product_id that could fit. This fix ensures that lines without product_id are taken into account when trying to predict a product. Followup on #30906 opw-2986213 Forward-Port-Of: odoo/enterprise#31976 Forward-Port-Of: odoo/enterprise#31922
Migrate `planning_calendar` to the new wowl2 calendar views. Mixins have been duplicated as hooks for those views. Forward-Port-Of: odoo/enterprise#31940
Original PR description
Migrate `planning_calendar` to the new wowl2 calendar views. Mixins have been duplicated as hooks for those views. Forward-Port-Of: odoo/enterprise#31940
…ss to hr_contract Currently, the display of the Payroll account when hr_work_entry_contract_enterprise is installed is not restricted. A user with no access to hr_contract could see the Payroll icon while not being able to access the app due to an access error on hr_contract. This commit hides the Payroll app icon if the user doesn't have hr_contract rights. task-2994285 Forward-Port-Of: odoo/enterprise#31982 Forward-Port-Of: odoo/enterprise#31788
Original PR description
…ss to hr_contract Currently, the display of the Payroll account when hr_work_entry_contract_enterprise is installed is not restricted. A user with no access to hr_contract could see the Payroll icon while not being able to access the app due to an access error on hr_contract. This commit hides the Payroll app icon if the user doesn't have hr_contract rights. task-2994285 Forward-Port-Of: odoo/enterprise#31982 Forward-Port-Of: odoo/enterprise#31788
This component doesn't need to be a LegacyComponent since it doesn't use the trigger_up anymore. Component is also not used anymore. Forward-Port-Of: odoo/enterprise#31981
Original PR description
This component doesn't need to be a LegacyComponent since it doesn't use the trigger_up anymore. Component is also not used anymore. Forward-Port-Of: odoo/enterprise#31981
It shouldn't be possible to create payments from the Batch Payment form view. Create option was removed for 15.0 in https://github.com/odoo/enterprise/pull/16705, so this PR returns it to how it was. Forward-Port-Of: odoo/enterprise#31942
Original PR description
It shouldn't be possible to create payments from the Batch Payment form view. Create option was removed for 15.0 in https://github.com/odoo/enterprise/pull/16705, so this PR returns it to how it was. Forward-Port-Of: odoo/enterprise#31942
In hr_appraisal, when a user is added in the manager_ids field and is not the manager of the employee having his appraisal, he is not able to edit the appraisal. This commit updates the ir rule to allow user added in the manager_ids field to write the appraisal. task-2993820 Forward-Port-Of: odoo/enterprise#31978 Forward-Port-Of: odoo/enterprise#31705
Original PR description
In hr_appraisal, when a user is added in the manager_ids field and is not the manager of the employee having his appraisal, he is not able to edit the appraisal. This commit updates the ir rule to allow user added in the manager_ids field to write the appraisal. task-2993820 Forward-Port-Of: odoo/enterprise#31978 Forward-Port-Of: odoo/enterprise#31705
Different dashboard fixes were added in this commit: - When you have a lot of payslip batches for example, each panel in the payroll dashboard will occupy a lot of space. After this commit, a maximal space is defined and information will still be accessible through scrolling in the panel. - the warning about invalid bank account will only take users with a running contract. - background-color change from blue to gray for the state 'new' in batches to distinguish it from 'done' batches. - lim
Original PR description
Different dashboard fixes were added in this commit: - When you have a lot of payslip batches for example, each panel in the payroll dashboard will occupy a lot of space. After this commit, a maximal space is defined and information will still be accessible through scrolling in the panel. - the warning about invalid bank account will only take users with a running contract. - background-color change from blue to gray for the state 'new' in batches to distinguish it from 'done' batches. - limit the width of batch names to avoid broken views task-2985067 Forward-Port-Of: odoo/enterprise#31907 Forward-Port-Of: odoo/enterprise#31802
Mirrors community changes (https://github.com/odoo/odoo/pull/100606). Removes proprietary fonts and allow the OS to use the system ones. The aim is to reduce http request and the general footprint. The new font-stack (defined in community): ``` - apple-system (San Francisco): iOS Safari, macOS Safari, macOS Firefox - BlinkMacSystemFont (San Francisco): macOS Chrome - Segoe UI: Windows - Helvetica Neue: old OSX versions - Roboto: Android, Chrome OS - Ubuntu: Ubuntu - Liberation S
Original PR description
Mirrors community changes (https://github.com/odoo/odoo/pull/100606). Removes proprietary fonts and allow the OS to use the system ones. The aim is to reduce http request and the general footprint. The new font-stack (defined in community): ``` - apple-system (San Francisco): iOS Safari, macOS Safari, macOS Firefox - BlinkMacSystemFont (San Francisco): macOS Chrome - Segoe UI: Windows - Helvetica Neue: old OSX versions - Roboto: Android, Chrome OS - Ubuntu: Ubuntu - Liberation Sans: Linux (others) - Arial: Any - sans-serif: General fallback ``` community: - https://github.com/odoo/odoo/pull/100606 task-2995248 Forward-Port-Of: odoo/enterprise#31529
Currently, when a manager wants to reopen an appraisal to correct a small mistake, the corresponding activities are recreated. This commit prevents the creation of these activities when an appraisal goes from the 'done' stage back to the 'confirmed' state. To ensure that people can't just silently make changes to appraisals this way after the fact, followers will be notified when appraisals are set to 'done'. task-2983617 Forward-Port-Of: odoo/enterprise#31305
Original PR description
Currently, when a manager wants to reopen an appraisal to correct a small mistake, the corresponding activities are recreated. This commit prevents the creation of these activities when an appraisal goes from the 'done' stage back to the 'confirmed' state. To ensure that people can't just silently make changes to appraisals this way after the fact, followers will be notified when appraisals are set to 'done'. task-2983617 Forward-Port-Of: odoo/enterprise#31305
*Someone* forgot to call `super.setup()` in the kanban overrides. Forward-Port-Of: odoo/enterprise#31923
Original PR description
*Someone* forgot to call `super.setup()` in the kanban overrides. Forward-Port-Of: odoo/enterprise#31923
In the following commit: dd7f4d501a4d23b04a1899be8fd51cc583673c9d - We had new fields for `stock.picking.type`; - We had a method who check these fields's value in the `create` and in the `write`; - We force `restrict_scan_source_location` to `mandatory` in the data for the outgoing picking type. Those cause an issue: when setting the warehouse's outgoing shipments setting in 3 step (pick-pack-ship), the check method raises the error. It was because the `_create_or_update_sequences_and_pic
Original PR description
In the following commit: dd7f4d501a4d23b04a1899be8fd51cc583673c9d - We had new fields for `stock.picking.type`; - We had a method who check these fields's value in the `create` and in the `write`; -…
In the following commit: dd7f4d501a4d23b04a1899be8fd51cc583673c9d - We had new fields for `stock.picking.type`; - We had a method who check these fields's value in the `create` and in the `write`; - We force `restrict_scan_source_location` to `mandatory` in the data for the outgoing picking type. Those cause an issue: when setting the warehouse's outgoing shipments setting in 3 step (pick-pack-ship), the check method raises the error. It was because the `_create_or_update_sequences_and_picking_types` warehouse method call `update` for every fields one by one, meaning when we want to update `restrict_scan_source_location` and `restrict_scan_dest_location`, it write first the `restrict_scan_source_location` which will raise the error because it doesn't update yet `restrict_scan_source_location` (and so, we have the forbidden couple "mandatory"/"optional"). Maybe we should call `write` instead of `update` in the warehouse's method, but that said, it should be better to have a SQL constraint instead of a method call in `create`/`write`. So, this commit replaces this method by a SQL's check constraint. Also, to do that, we have to force 'restrict_scan_dest_location' on 'no' for the outgoing picking type otherwise the constraint is violated by the data and can't be added. Forward-Port-Of: odoo/enterprise#31642
The popover adaptation to bootstrap 5 was omitted. This popover is in the manual reconciliation widget, on each bank statement line. Forward-Port-Of: odoo/enterprise#31953
Original PR description
The popover adaptation to bootstrap 5 was omitted. This popover is in the manual reconciliation widget, on each bank statement line. Forward-Port-Of: odoo/enterprise#31953
With a previous big commit, the enterprise inheritance of open_move was omitted, and clicking on the move_name of an account move line corresponding to a bank statement would not open the bank reconciliation widget anymore. Forward-Port-Of: odoo/enterprise#31828
Original PR description
With a previous big commit, the enterprise inheritance of open_move was omitted, and clicking on the move_name of an account move line corresponding to a bank statement would not open the bank reconciliation widget anymore. Forward-Port-Of: odoo/enterprise#31828
Most companies have one plan, and we don't want to open a report on one line. Thus, we still group by account but no longer by plan by default. Forward-Port-Of: odoo/enterprise#31901
Original PR description
Most companies have one plan, and we don't want to open a report on one line. Thus, we still group by account but no longer by plan by default. Forward-Port-Of: odoo/enterprise#31901