Friday, November 8, 2024
10 changes · 18.0
Resolved issues and error corrections
This fix corrects misleading location labels and help text shown when configuring stock and repair operation types. It makes the wording more consistent and avoids confusion for users working with repairs, inventory transfers, or manufacturing flows.
Original PR description
Followup to task: 4028900 Fixes the following issues: - The label of "Default Component Destination Location" was applied to all operation types, not just `repair_operation`. This resulted in…
Followup to task: 4028900 Fixes the following issues: - The label of "Default Component Destination Location" was applied to all operation types, not just `repair_operation`. This resulted in confusing labeling for all the other operation types when Repair was installed - The "help" of `default_location_src_id` and `default_location_dest_id` referred to stock pickings, but these fields are also used for MRP and Repair. So the help has been updated to be more generic to avoid confusion - Task: 4034713 removed the "Default" from the label of the default location fields for picking types, therefore we remove them from the repair ones for consistency - cleaned up the inheritance of the picking type form view in repair so that the `default_location_src_id` field isn't in the same view twice (or have inconsistent attributes) - reordered the Repair default locations to follow a more logic ordering --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The loyalty card point update wizard now automatically shows the card's existing point balance. This helps users adjust loyalty points with the correct starting value and reduces the chance of manual errors.
Original PR description
Issue: -The old balance field in loyalty card point update wizard is not set by default Fix: -Added `card_id` in form view
This update improves automated checks for website shop features so they run faster and fail less often. It fixes several test flow issues around product search, autocomplete, gift cards, loyalty, and delivery, helping maintain stability without changing customer-facing behavior.
Original PR description
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 fixes a typo in the Expenses app. It is a minor cleanup that improves text clarity without changing business workflows or functionality.
Original PR description
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 change fixes the setup of an automated Mail discussion walkthrough so it starts after other functional tours and opens at the correct place. This helps ensure the tour reliably shows the expected in-app guidance during testing and validation.
Original PR description
In this commit, we fix the sequence and the url of discuss_channel_tour tour with the aim to start in last position after all the functional and with the aim to see the baball on the app. task~4309858 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 fixes an automated test so it works correctly when only the Community edition is installed. It helps keep quality checks reliable and avoids false failures during validation, with no expected impact on users.
Original PR description
Fixes a test to work without enterprise installed. Runbot Error 105489
This fixes how import batch size limits are passed to the file handling component. It ensures the configured size is understood correctly, helping imports respect the intended limits and avoid incorrect batching behavior.
Original PR description
This commit fixes the parameters send to the BinaryFileManager. There was a typo `maxBatchSize` and not `maxSizePerBatch` also has the unit on the web interface is in mega we should multiply the unit by 1024 ^ 2 to have the correct value. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an automated Studio walkthrough so it properly handles the export confirmation window. The change helps keep quality checks reliable without changing how business users work in Studio.
Original PR description
At the end of the tour, when we want to export all modifications, it opens a modal from v18.0. But, as it is not allowed to do action on element that's below a modal, the tour fails. In this commit, we click on export button to test the export feature and then close the modal before continuing the tour.
This fix updates spreadsheet chart tests so they match the latest trend line calculation behavior. It helps keep automated checks reliable after a calculation change, with no expected impact on everyday users.
Original PR description
Since o-spreadsheet/commit/9909fa98d data points are normalized to compute the trend line. Those 2 tests were computing a 2nd order polynomial trend line based on 2 data points only, which doesn't really makes sense. With only 2 points, the normalized labels become [0, 1]. The matrix is of the form x1 x2 x1^2 x2^2 it gives 0 1 0 1 with [0, 1] as the labels. This matrix is not invertible since the two lines are the same and the determinant is 0.
The map view now removes an unnecessary gap between each group title and its list of records. This makes grouped map results easier to scan and gives the interface a cleaner, more polished appearance.
Original PR description
Before this commit: There is an excessive gap between the group title and the list of records. After this commit: The excessive space between the group title and the list of records has been removed. Task-4295965