Navigate
Branch
Thursday, May 23, 2019
10 changes
Enhancements to existing features
This change lets Odoo tests run even when demo data has not been loaded. It supports better testing practices by allowing tests that create their own data to run in leaner environments.
Original PR description
As most of the tests are using demo data, a check is performed to verify that they are loaded. A best practice is to write tests that does not depend on demo data but with this check, it's not possible to launch them without demo data. With this commit, the check is removed, allowing to launch test even without demo data loaded.
This change updates how Odoo handles unsaved records while users edit forms, making related field updates more consistent and reducing special-case behavior behind the scenes. It affects several business areas such as accounting, HR leave, mail, manufacturing, products, and website events, helping prevent errors during on-screen changes before records are saved.
Original PR description
Using new records in onchange() simplifies code: the environment flag `in_onchange` is gone, and all special cases correspond to new records. The expression `record._origin` is now available on *all* records, and returns the *actual* record corresponding to `record`.
This change adds a safeguard test for accounting reconciliation to ensure write-offs keep debit and credit amounts on the correct side. It helps prevent future changes from introducing errors in financial reconciliation results.
Original PR description
Test that there is no conversion of debit/credit when creating a writeoff with the method process_move_lines of the model 'account.reconciliation.widget'. 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
Kit orders now use the routes of their individual components instead of the kit product itself, making fulfillment behavior more accurate. Availability and delivered quantities are calculated from component stock and processed quantities, so sales teams get clearer warnings and more reliable delivery status for kits, including complex cases like backorders, returns, nested kits, and different units of measure.
Original PR description
**Before this PR:** - The routes applied when a kit was ordered was the ones set on the kit. - The quantities available when a kit was ordered was 0 even if enough components were available - The…
**Before this PR:**
- The routes applied when a kit was ordered was the ones set on the kit.
- The quantities available when a kit was ordered was 0 even if enough components were available
- The quantities delivered when a kit was ordered were correct only if all move from the picking of its sale order were done. So the quantities delivered were correct only if all components were fully delivered.
**After this PR:**
- The routes of each components of the kits are applied independently and the routes set on the kit itself are ignored
- A 'next activity' is logged when a kit as the route 'Manufacture' set
- The number of kits available is computed based on the quantities available of the components needed to make the kit.
- The number of kits delivered is computed based on how many kits it's possible to make with the components already processed.
- Some test case are added the check the flows when kits are ordered.
Those test case make sure that:
* Delivered quantities are accurate if :
- kits in kit
- backorders are made
- returns are made
- returns of returns are made
- Multiple differents UoMs are setted on the components of a kit
* Available quantities are accurate if:
- Kits in kit
- Multiple differents UoMs are setted on the components of a kit
TaskID : 1863856
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update simplifies how draft form changes are handled before records are saved, reducing special-case behavior behind the scenes. It helps make field updates more consistent in Field Service, Manufacturing Work Orders, and Subscriptions without introducing major user-facing changes.
Original PR description
Using new records in onchange() simplifies code: the environment flag `in_onchange` is gone, and all special cases correspond to new records. The expression `record._origin` is now available on *all* records, and returns the *actual* record corresponding to `record`.
Resolved issues and error corrections
This update corrects the Lithuanian locale date format to use hyphens instead of dots, aligning it with the ISO-style format used in Lithuania. Business users working in Lithuanian will see dates displayed in the expected local format, reducing confusion in records and documents.
Original PR description
Lithuania uses date format `yyyy-mm-dd`, not `yyyy.mm.dd`. LST ISO 8601:1997 (obsolete) LST ISO 8601:2006 (current) Description of the issue/feature this PR addresses: changing LT date format Current behavior before PR: Incorrect date format for LT localization. Desired behavior after PR is merged: Correct date format for LT localization. https://en.wikipedia.org/wiki/Date_format_by_country https://en.wikipedia.org/wiki/ISO_8601 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The leave statistics widget was adjusted to avoid newer JavaScript syntax that some supported older browsers cannot run. This helps keep the time off feature working consistently for users on legacy browsers and devices.
Original PR description
This commit fix non-compliant JS code syntax. Currently Odoo JavaScript code base supports ECMAScript <= 5 only Using ECMAScript 6 (2015) feature break compatibility with Internet Explorer and Android KitKat (4.4) Ref: https://eslint.org/docs/rules/object-shorthand
PDF work instructions in Manufacturing now open in the previewer instead of showing an error. The fix corrects how PDF files are retrieved, helping users access instructions without interruption.
Original PR description
**Error in the preview of a PDF** Steps to Reproduce: - Go to Manufacturing - Go to Work Order of a record - Check the 'Work Instruction' This happens due to a minor problem with the rendering of PDF. Wrong URI for pdf file is set. This PR will fix that problem. Task Link: https://www.odoo.com/web?#id=1986709&action=327&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.1333c7b822f687554b0c740e08402357 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The “Track this page” option now fills in the actual landing page URL instead of leaving the default placeholder text. This makes link tracking easier and helps website users create accurate tracked links without manually correcting the URL.
Original PR description
Description of the issue/feature this PR addresses: - Related task: https://www.odoo.com/web?#id=1998160&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 - Pad: https://pad.odoo.com/p/r.9ef1cdcfe02be267c910b86580ef47ee 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
Features or functions removed from Odoo
The Project app no longer includes an unused notes field on tasks. This cleanup reduces unnecessary data fields and helps keep task records simpler without affecting normal project workflows.
Original PR description
Pad:https://pad.odoo.com/p/r.d037957a946d2489bba5018a9a10f8a8 Task:https://www.odoo.com/web#id=1986384&model=project.task&view_type=form&menu_id=