Friday, January 31, 2025
8 changes · 17.0
Resolved issues and error corrections
This update adjusts a manufacturing test so that tiny timing differences no longer cause false failures. It helps keep automated checks stable without changing how users work with the manufacturing app.
Original PR description
Comparing times may give false error because of the precision and time to run a test. This commit adds a delta into which two datetime are considered the same in order to not make the test failing by mistake. runbot : 112119 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
This update clarifies which payment journal data should be used when preparing check printing information. It helps avoid conflicts for businesses that use custom extensions, while causing no expected change for standard users.
Original PR description
This issue is not directly an Odoo issue, but it can create an issue if a custom module adds a field called journal_id to the account.payment model. There are no knock-on effects of this, because anyway the original developer should have specified the table. Additionally, it seems that there was a mild typo in the line before it that didn't affect anything. I see no harm in fixing it. Description of the issue/feature this PR addresses: Current behavior before PR: No change in behavior. Desired behavior after PR is merged: No change in behavior. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The partner merging wizard now handles custom reference fields added by third-party modules without causing an error. This improves reliability for businesses using customized Odoo setups, while native Odoo behavior remains unchanged.
Original PR description
Description of the issue/feature this PR addresses: Fix a traceback with the partner merging wizard. Current behavior before PR: Currently, the partner merging wizard doesn't support fields of type `reference`, because this type of field is never used by Odoo on model `res.partner`. This will never happend in native Odoo, but some external addons can trigger this traceback. Desired behavior after PR is merged: The traceback is fixed and reference fields are treated like any others field types. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The depreciation schedule now keeps selected account sections expanded when users refresh or print the report. This makes printed reports match what users saw on screen and brings the behavior in line with other reports.
Original PR description
If "Unfold All" is not selected and "Group by Account" is, printing the Depreciation Schedule won't print the unfolded lines. Furthermore, if you unfold some lines and then refresh, all the lines are refolded. This behaviour is different than the other reports, where the lines you unfold are printed and remembered during a refresh. The fix is to mark the parent lines generated by `group_by_account` as unfolded if the line is present in `options['unfolded_lines']`. task-4507580
The Brazilian localization now includes the latest official NCM product classification data from the Brazilian government. This helps businesses keep tax-related product information current, with new codes added and existing descriptions refreshed without removing any current codes.
Original PR description
Using the latest data from the Brazilian government [1]. No codes were removed, this contains only new codes and description updates to existing ones. [1] https://www.gov.br/receitafederal/pt-br/assuntos/aduana-e-comercio-exterior/classificacao-fiscal-de-mercadorias/download-ncm-nomenclatura-comum-do-mercosul opw-4522735
Messages sent from Odoo chats to WhatsApp now preserve line breaks entered with Shift+Enter. This prevents words from being accidentally joined together, making customer communications clearer and easier to read.
Original PR description
Before this commit: When a user in Odoo uses the dialog box to send a message to a WhatsApp number and inserts a line break with "Shift+Enter," it creates a <br> tag. In the WhatsApp module, these tags are stripped, causing the word before and the word after the <br> tag to be joined together without a space or a line break to separate them. How to reproduce: Send a message via the dialog box to a WhatsApp number and insert a line break using Shift+Enter. On the phone, the line break will not be present anymore because the tag <br> is removed with the other tags. After this commit: the line break is there and the words are not join together anymore. OPW-4079729
The subscription stock tests now use a fixed subscription start date and a longer invoice generation window. This prevents date-sensitive test failures where expected deliveries were not created, improving reliability without changing business functionality.
Original PR description
Before this commit, the test was relying in "today's" date for creating the recurring invoices. Since the time period for generating them was too short, the expected deliveries were not being generated. After this commit, we give a fixed date to the start date of the subscriptions and then generate the recurring invoices with a time distance of a month, solving the issue. Issue-from: OPW-4166852 Related PR: odoo/enterprise#73397
Creating an appointment from the calendar view now preserves the selected resource booking instead of accidentally removing it. This prevents lost resource reservations when users switch from Gantt to calendar view and schedule appointments with resources.
Original PR description
Steps to reproduce: 1. Go to appointments 2. Select any appointment with resources. 3. Change from the gantt view to the calendar view. 4. Create a new event from the calendar view with resource_id set. Issue: Since in this form we are using the `resource_id` and not the `appointment_resource_id` the inverse computation from `_inverse_appointment_resource_id_or_capacity` will think that we have removed the linked resource_id from the appointment so we will remove the booking line. Solution: We might assume that when having only 1 `resource_id`, this one will be the one to be used for the appointment, the `appointment_resource_id` and we should not get rid of the booking line. opw-4440569