This update ensures that the l10n_id_reports module is properly configured for translation management within Odoo. By adding the module to the .weblate.json file, the system can now track and manage translations for this reporting module, improving its usability for users in countries that speak Icelandic.

Enable translation management by adding the
module entry to .weblate.json.

task-6239169

Forward-Port-Of: odoo/enterprise#118931

This update corrects a technical oversight where a new module for the Hungarian reports (l10n_hu_reports_a60) was developed but not properly integrated into the Weblate translation system. This ensures accurate translations are available for users in Hungary, preventing potential communication issues.

We added a new module here 379c5e9611f1f1c242027c1c134219966474de16
but forgot to add it to weblate.json for
translation.

no-task

Forward-Port-Of: odoo/enterprise#118932

This update resolves an issue where the ellipsis indicator for long text messages didn't always update correctly in the Enterprise version of Odoo. The change utilizes a more efficient, reactive approach (signals) to ensure the indicator resets immediately when new text is added, improving the user experience.

This update corrects a problem where Odoo reports were displaying incorrectly when all company journals were assigned to a single ledger. The change removes the 'Local GAAP' implicit ledger from report selections, ensuring accurate reporting regardless of ledger configurations. This improves the reliability of financial reports.

When all journals of the company are in a ledger, the implicit ledger 'Local GAAP' is empty, so we remove it from the ledger selection in the reports.

task-6260588

Forward-Port-Of: odoo/enterprise#118927

This update clarifies how subscription prices are set up. Previously, the system automatically filled in pricelists, leading to user confusion about price scope. Now, users manually select the pricelist, eliminating errors and simplifying the subscription pricing process.

When adding a new pricing rule on a subscription product (either from the product form's Prices tab or from the subscription plan's Pricing page), we was pre-filling the pricelist field with the company's first available pricelist. This caused confusion because users assumed the price would apply to all pricelists, while it was actually scoped to that one pricelist only. This led to broken combinations on the eCommerce product page and required an extra manual step to clear the pricelist for each rule added.

task-6154318

This update automatically fixes formatting issues in the Obox modules, ensuring consistent code style. The changes were made to improve code readability and maintainability, aligning with our development standards. This work is part of an automated process enforced by Odoo's linting system.

This commit fixes all Prettier formatting errors in the Obox modules. The lint check itself is enforced in odoo/odoo#267994.

This update optimizes the way Odoo calculates the display of work orders, specifically within the MRP module. By changing a selector used in the code, the system now recalculates styles more efficiently, leading to faster performance during common actions like resizing windows or scrolling through large tables.

Avoid using the :has() selector and use a specific class on the body instead to replicate the same behavior, this reduces work during the "Recalculate Style" phase.

It lowers recalculation time during window resizes, heavy scrolling, and table sorting by preventing broad selector matches and limiting style checks to elements with the specific class.

Forward-Port-Of: odoo/enterprise#119024
Forward-Port-Of: odoo/enterprise#118618

A test was failing due to a limitation in how the POS system loads partner data. This fix ensures that all partners are properly searched for, resolving the test failure and improving the reliability of the point-of-sale tax functionality. This primarily impacts the US partner search functionality.

**Issue:**
`test_pos_fiscal_position_without_pos_avatax` test is failing with demo data because a US partner is created and searched for in the tour, but only the first 100 partners (alphabetically ordered) are loaded in the POS.
Therefore, he's not found.

runbot-938983

Forward-Port-Of: odoo/enterprise#118345