Thursday, March 28, 2024
10 changes · 17.0
New functionality added to Odoo
This update adds support for the Zona Franca Fiscal Position in Uruguay's accounting configuration. While this feature will be used for electronic data interchange (EDI) in the future, it is being added now to ensure it is properly created when the accounting system is initially set up. This prepares the system for upcoming EDI functionality.
Original PR description
This one will be used for EDI in the future, but we leave it here because we need this one is created when loading the accounting configuration --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
The 'Removal strategy' field in the stock location form is now automatically hidden when users select location types other than Internal. This improves the user interface by only showing relevant fields based on the selected location type, making the form cleaner and less confusing for warehouse managers.
Original PR description
In this commit: ================== Invisible the 'Removal strategy' field when selecting the other location type except the Internal location. task-3555853 Forward-Port-Of: odoo/odoo#154117
Resolved issues and error corrections
This fixes an issue where clicking a day in the Time Off Gantt view could prefill the request with the previous day as the start date. Users now get the expected same-day start and end dates, helping avoid incorrect leave durations and approval confusion.
Original PR description
STEP TO REPRODUCE :
===================
1- Go on time off
2- Select Approvals/Time off
3- select gantt view
4- Click on a 22 february
You will see these default dates : 21 february and 22 february instead of 22 february and 22 february and sometimes you will have a duration of 1 days and sometimes of 2 days.
Task: 3792515Miscellaneous changes
**Current behavior:** If a recurring sale order has an associated sale order option and the recurring plan of the order is changed, a trace back occurs. **Expected behavior:** The recurring plan can be changed as it ordinarily would. **Steps to reproduce:** 1. Add a recurring product to a sale order 2. Add an optional recurring product to the order 3. Try to change the recurring plan of the order to encounter the trace back **Cause of the issue:** This flow causes some 'phanto
Original PR description
**Current behavior:** If a recurring sale order has an associated sale order option and the recurring plan of the order is changed, a trace back occurs. **Expected behavior:** The recurring plan can…
**Current behavior:** If a recurring sale order has an associated sale order option and the recurring plan of the order is changed, a trace back occurs. **Expected behavior:** The recurring plan can be changed as it ordinarily would. **Steps to reproduce:** 1. Add a recurring product to a sale order 2. Add an optional recurring product to the order 3. Try to change the recurring plan of the order to encounter the trace back **Cause of the issue:** This flow causes some 'phantom' sale order lines to have their price recalculated (phantom because they have no price, qty, currency, nor order_id field values). During this recalculation a currency_id is expected either in the line itself or in the sale order it is a part of. Because there is no value for either of these, it fails the ensure_one() method in the sequence (0 vals, expects 1). The phantom lines are created in the `sale.order.option` model in the `sale_management` module, in `_compute_price_unit()` and `_compute_discount()`. **Fix:** Call `invalidate_recorset(flush=False)` on these cached records at the end of the methods in which they are created. Test added in https://github.com/odoo/enterprise/pull/58264 opw-3754297 Forward-Port-Of: odoo/odoo#157515
This update removes unnecessary pricelist creation and modification from Field Service sales tests to comply with new system rules that prevent changing pricelists on confirmed sales orders. The tests continue to work correctly without these steps, ensuring compatibility with recent platform changes.
Original PR description
Changing the pricelist on a confirmed SO is now forbidden. It was done in a fsm test, but the test is working fine without the pricelist, so the pricelist creation and SO update has been removed. See also: https://github.com/odoo/odoo/pull/157742
This update fixes a test issue in the Sales Subscription module by properly clearing temporary test records. The fix ensures tests run cleanly without leaving behind residual data that could interfere with other tests or cause unexpected behavior.
Original PR description
**Coverage for community fix** https://github.com/odoo/odoo/pull/157515 opw-3754297 Forward-Port-Of: odoo/enterprise#58264
This update corrects a naming inconsistency in the Swiss payroll module where input types and salary attachment types didn't match their corresponding rule names. The fix ensures that payroll rules, input types, and salary attachments are properly aligned, which prevents potential processing errors and improves data consistency in Swiss HR payroll operations.
Original PR description
Input type and salary attachment type should match the rule name task-3835119
Fixed an issue where the timesheet timer display width would shift when users clicked the start button. The fix ensures the timer header maintains a consistent width before and after starting a timer, providing a more stable and professional user experience.
Original PR description
Steps: - install time sheet module - click on start button - before clicking on start button,width is different - after clicking on start button ,width is different Issue: - the width is unstable,seems different before and after clicking on start button Cause: - The problem occurs because of height issue solution: - if we give the height to that class the problem will be solved task-3645747 Forward-Port-Of: odoo/enterprise#50100
This update fixes inconsistent test failures in the website shop module that were occurring during automated builds. The changes improve how product variants are created and tested to ensure more reliable and predictable test results. This helps maintain the stability of the e-commerce platform's automated quality checks.
Original PR description
Wild try to avoid failures on runbot builds (not reproducible locally). * simplify and split tour steps * correctly specify check steps as isCheck: true * make sure python setup is deterministic * batch template creation to avoid creation of dummy archived variant * target values for the variant to archive instead of its number in the list of variants runbot build error 25046 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#159270
A test that verifies company deletion now works with onboarding records has been temporarily disabled. The test was causing issues in real-world scenarios where other modules create related records that prevent company deletion. The team will implement a more robust solution that works across all module configurations.
Original PR description
In https://github.com/odoo/odoo/commit/8e3283aabfd93a78eb4d72c4fd97f6a20ad08ef4 we solved the issue of onboarding progress records preventing the deletion of a company. We also added a test for this solution. In practice, it will not always make sense nor will it be allowed to delete a company and in some cases, the first thing that would fail is a foreign key from another model where it wouldn't make sense to cascade as we do for onboarding progress. Some modules create related records when a company is created such that it would be cumbersome to bypass that. Therefore, we disable this test until a clean flow robust to all sorts of installed modules configuration is implemented. See runbot 60475 Task-3829936 Forward-Port-Of: odoo/odoo#159337