Friday, July 18, 2025
3 changes · 18.0
Enhancements to existing features
This update improves Odoo's internal Hoot testing tools so automated tests run more reliably, start faster, and use less memory in headless environments. It also makes test filtering and result handling clearer, helping development and quality teams diagnose issues with less friction while keeping changes limited to the testing ecosystem.
Original PR description
## Pull Request HOOT (PRHOOT) 35 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Purchase order lines linked to a project now retain their existing analytic allocations while also adding the project’s allocation when there is no conflict. This improves cost tracking accuracy by ensuring project-related purchases are reflected without overwriting manually entered or model-based distributions.
Original PR description
Currently, if a purchase order line has an analytic distribution and then a project with an analytic account is added to the PO, the project analytic distribution is not added. Only in lines without any analytic distribution, the projetc account is added as expected. This commit modifies `_compute_analytic_distribution()` to keep both the project account and the existing analytic distribution (that were added manually or from a distribution model) in all PO lines where the analytic plans do not conflict. task-4904044 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Italian e-invoicing registrations now include an additional identifier, such as the VAT number, so incoming vendor bills can be matched to the correct registered user more reliably. This helps prevent processing failures when documents contain only a VAT number instead of the main identifier.
Original PR description
This improvement addresses an issue in the Italian e-invoicing (l10n_it_edi) and IAP registration logic where incoming vendor bills with only a VAT number failed to match the correct registered EDI user. Changes introduced: - Added `edi_identification_secondary` (e.g. VAT number) to support fallback user matching. - Updated the `/create_user` endpoint to accept and store the secondary identifier. - Modified `create_user` logic to send both primary and secondary IDs from Odoo. - Prepared the base for matching incoming invoices against both identifiers. See also: odoo/iap-apps#1056 Task [link](https://www.odoo.com/odoo/project/967/tasks/4619718) task-4619718