Friday, April 25, 2025
4 changes · master
Resolved issues and error corrections
Updated internal tests so fleet-related expense checks run with the right permissions. This helps prevent false test failures and keeps accounting and fleet expense features reliable during development.
Original PR description
Creating fleet objects requires being a fleet administrator or sudo. However because copying fleet objects (specifically vehicles) as well as posting moves *also* requires those rights, using sudo requires about 20 changes throughout the setup and tests. Maybe fleet will eventually want some more specificity in their test ACL management, but just setting the current user as fleet admin seems to do a good job while avoiding most of the mess. https://runbot.odoo.com/odoo/error/163135 https://runbot.odoo.com/odoo/error/181531
The Documents accounting action now uses the correct label, "Create Vendor Credit Note," instead of "Create Vendor Refund." This avoids customer confusion and keeps the wording consistent with the accounting form that opens from the button.
Original PR description
TLDR: reword "Create Vendor Refund" => "Create Vendor Credit Note" During the refactoring in https://github.com/odoo/enterprise/commit/a32825ee00f2b330d99113f4d8c1488903fe744e The enum value of "account.move.in_refund" was used to name the button "Create Vendor Refund" instead of its string "Vendor Credit Note" when converting the action into the new documents actions scheme. This is confusing for customers (since it is not always a refund) and is inconsistent with the rest of the user facing wording (i.e. the form view that opens when the button is clicked on). Reported/noticed during: opw-4488038
Fixed how pivot table date formulas are generated in spreadsheets by removing unnecessary spaces before the day and month values. This helps dates display and calculate consistently when users work with spreadsheet pivots.
Original PR description
Removed extra spaces in front of the day and month in DATE function. Task: 4725023
The Planning list view now keeps planned date fields more compact when edited, preventing the arrow between start and end times from appearing out of line. This improves visual consistency and makes the schedule easier to read for users working in list view.
Original PR description
With this commit ============= In the Planning module, the Planned Date field in the list view was visually misaligned when edited. The arrow (->) between the start and end times would appear off-center compared to other rows. Previously, the field had a width of 425px. This commit reduces the width to 325px to keep the input field more compact and ensure the arrow and date values remain visually aligned across all rows in both view and edit modes. Steps to Reproduce: 1. Go to Planning. 2. Switch to list view. 3. Click to edit the Planned Date field. 4. Observe that the arrow is vertically misaligned due to the input's size. This fix improves visual consistency in the list view by constraining the field's width. Task: 4607249