Tuesday, October 15, 2024
13 changes
6 changes
Enhancements to existing features
The planning time-off module's automated tests were moved to a newer testing framework. This helps keep future maintenance more reliable without changing day-to-day user behavior.
Original PR description
Purpose of this PR: This PR aims to convert QUnit tests which rely on mail/test_utils to hoot. Part of task: 3818666
Users processing Indian vendor bills can now type an IRN manually when scanning is not possible or convenient. This reduces friction in bill entry workflows by providing an alternative to QR code scanning while reusing shared barcode entry components.
Original PR description
This commit introduces a manual IRN entry option. As of now, only the QR code scan option is available, now the user can enter the IRN number manually. Steps:- - Open Vendor Bills - Click on the scan button - Click on Tap to scan the Bill button A new input is provided to enter IRN number manually. This Commit moves the file `manual_barcode.js` and `manual_barcode.xml` to barcodes module which is in community version. Com PR - https://github.com/odoo/odoo/pull/171934 task-4022648
The accounting reports tests now set the country before applying country-based availability rules. This keeps the test process aligned with the latest validation requirements and helps prevent avoidable failures during development.
Original PR description
In the community PR, a constraint on the availability_condition was added, where if availability_condition is set to country, the country_id should be set. Therefore, in tests where the availability condition is set to country, the country should be set before. task-4160643
This update aligns internal Python class names with their corresponding Odoo model names across accounting-related modules. It improves code consistency and maintainability without changing day-to-day business workflows.
Original PR description
see: https://github.com/odoo/odoo/pull/178200
GSTR-1 reporting for Indian GST is now calculated from journal entries rather than lower-level journal items. This should make the generated GST return data more accurate and efficient, including for point-of-sale related reporting.
Original PR description
In this PR the GSTR-1 computation process has the following changes: - Switch to Journal Entries: GSTR-1 JSON computation is now based on journal entries instead of journal items. - JSON Retrieval: Fetch JSON data from the `l10n_in_gstr_json` field in journal entries and adjust all GSTR-1 computations accordingly. - Method Removal: Moved the `_get_tax_details()` in `l10n_in` and removed `_get_section_domain()` method as it is no longer necessary. - Section Determination: The GST section is now determined using the `l10n_in_gstr_json` and `l10n_in_gstr_section` fields in journal entries. - Method Update: Adjusted the `l10n_in_round_value` method call to reflect its shift from `account.edi.format` to `account.move`. These improvements streamline the GSTR-1 computation process and enhance the accuracy and efficiency of GST reporting. task id: 3941950 related PR: https://github.com/odoo/odoo/pull/173851
6 changes
Enhancements to existing features
The portal now checks that a selected state or province matches the chosen country and requires it when the country’s rules make it mandatory. This helps prevent incorrect or manipulated address data from being submitted, improving data quality and reducing downstream errors.
Original PR description
Description of the issue/feature this PR addresses: Currently, there is no validation ensuring the selected state corresponds to the chosen country, nor checks that enforce a state selection when required by the country. Current behavior before PR: Users can select a state that doesn't belong to the selected country. No validation exists to require a state selection when the country mandates it. Desired behavior after PR is merged: The selected state will be validated to ensure it belongs to the selected country. A state will be mandatory when the country requires it, and appropriate error messages will be shown when these conditions are not met. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Enhancements to existing features
This update improves how the system matches bills submitted late for GST reporting (GSTR2B). The matching process now uses the specific month of the bill date to find the correct bills, making the matching more accurate and reliable. This ensures businesses can properly reconcile their late bill submissions with their GST returns.
Original PR description
In this PR: - Updated the matching criteria for GSTR2B late bills to use the specific month of the bill date. - Replaced previous date filter on `invoice_date` to limit searches to the start and end of the bill's month. - Ensured accurate retrieval of bills by filtering based on the bill number and company. This change enhances the precision of bill matching in the GSTR2B late bill streamline process.
This update standardizes the names, categories, and short descriptions of service-related Odoo modules. It makes app listings clearer and more consistent for users browsing project, timesheet, helpdesk, field service, and planning features.
Original PR description
Cleaning of the name, category and summary of every module linked to services applications (project, timesheet, helpdesk, field service, planning) taskid:3524126
The portal now checks that a selected state or province matches the chosen country and requires it when the country rules say it is mandatory. This helps prevent incorrect or manipulated address data from being submitted, improving data quality and reducing downstream errors.
Original PR description
Description of the issue/feature this PR addresses: Currently, there is no validation ensuring the selected state corresponds to the chosen country, nor checks that enforce a state selection when required by the country. Current behavior before PR: Users can select a state that doesn't belong to the selected country. No validation exists to require a state selection when the country mandates it. Desired behavior after PR is merged: The selected state will be validated to ensure it belongs to the selected country. A state will be mandatory when the country requires it, and appropriate error messages will be shown when these conditions are not met. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can no longer manually create, update, or delete analytic items that are tied to journal items. This keeps analytic reporting aligned with the journal item's analytic distribution and prevents mismatched accounting data.
Original PR description
The analytic items related to a journal item are generated from the journal item's analytic distribution. But it is possible for a user, by accessing the analytic items view, to create/updtate/delete analytic items related to a journal item. The analytic distribution is then unsynced with the analytic items. With this commit, it is no longer possible, so the analytic items of a journal item will always reflect its analytic distribution. task-3977961
Developers can now adjust which website content containers are monitored for third-party iframe blocking through a dedicated website method instead of changing hard-coded logic. This keeps consent protection behavior intact while making customer-specific website customizations cleaner and safer to maintain.
Original PR description
Commit [958b41c4] added support to prevent 3rd-party iframes from loading without proper consent. As some iframes are built client-side, preventing them from loading required getting their container by their class. Those classes are stored in a set. Allowing any user to update that set does not make sense, but to make it possible for developers to update it through custos, this commit retrieves it from a method on the Website model instead of hard-coding it in the middle of a function. [958b41c4]: https://github.com/odoo/odoo/commit/958b41c4acec7e1700ca4d6e0b25ee0ad2aac9f1 task-4045932
Accounting reports can now group results by account code, making financial information easier to review and compare. This supports clearer reporting for businesses that rely on account-code based analysis.
Original PR description
PoC for TSB.
This update aligns the accounting app with a related platform change that prevents accidental changes or deletions of analytic entries tied to journal items. It helps preserve the integrity of accounting data while still allowing approved system processes to make necessary updates.
Original PR description
Adapt to community PR, which add a context key requirement in order to delete an analytic item related to a journal item. Community PR: odoo/odoo#182608 task-3977961