Friday, January 10, 2025
7 changes · 18.0
Resolved issues and error corrections
Calendar events created through modules such as Appointments will no longer automatically create follow-up activities when those modules do not need them. This avoids clutter and unnecessary work items for users when meetings are booked.
Original PR description
Some modules (i.e., Appointment) uses calendar.event, but they don't want to create an activity every time a user books a meeting. This PR indroduce a helper function, which return a list of models, in which we don't want to create activities. Task-4243603
This fixes an issue where the current user could appear twice in user selection dropdowns when search results reached the limit. Users now see the expected person once, in the correct position, reducing confusion when assigning or selecting users.
Original PR description
Steps: - Login as Mitchell Admin - Create 8 user (B, C, D, E, F, G, H, I) to reach search limit - Rename Mitchell Admin to Admin Mitchell to be the first result - Open a user dropdown (employee form) Actual result: - Admin Mitchell appears twice Expected result: - Admin Mitchell appears at first position - Admin Mitchell appears only once opw-4430590
This fix makes an automated recruitment website form test wait for the page element it needs before continuing. It reduces false failures in Odoo's test pipeline, helping keep recruitment website changes safer to release.
Original PR description
In this commit, we prefer to use selector in trigger instead of use native in run function. This is better to ensure trigger is in DOM when the run is activated. The findTrigger method in tour engine is based on MutationObserver while run function in a step definition is launched once the trigger has been found. This is why it can cause the following error during the tour. runbot-error-id~106439 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 fix makes an automated project to-do test more reliable by checking that tasks appear in the activity view without unnecessarily clicking them. It helps reduce false test failures and supports smoother maintenance of the project to-do feature.
Original PR description
Before this commit, the test running the `project_task_activities_split` tour could failed because a step clicks on a task displayed in the activity view instead of just checking if the task expected is present on the view. This commit removes the click event on that step to just check if we found the node with the trigger defined in that step to be sure the task is on the activity view. By doing that, the next step checking if another task is also there in the activity. Closes #192995
This update makes the Indonesian point-of-sale test setup more focused so it consistently finds the intended test product. It reduces random test failures, helping maintain confidence in future updates without affecting everyday users.
Original PR description
This fixes the indeterminate test failures where the Test Product isn't found in the product list. Related: https://github.com/odoo/enterprise/pull/76517
Long links in Social posts are now shortened with an ellipsis instead of overflowing outside kanban cards. This keeps post previews tidy and easier to read for users reviewing social content.
Original PR description
Before this commit: Post including long links were not truncated and will extend beyond the kanban card. This happen as the display CSS property is set to `inline` by default due to the <field> tag being transformed into a <span> tag in the HTML. <div> default display is `block` while <span> are `inline`. After this commit: The link truncate as intended with "..." Before:  After:  opw-4446906
Printed check reports now format the payee address correctly for top, middle, and bottom check layouts. This improves the appearance and readability of checks generated from payments, reducing the risk of poorly formatted printed documents.
Original PR description
Issue: ------ When printing the reports which are Print Check(Top, Middle and Bottom), the address of that particular report is not being formatted properly which makes the printed report poor…
Issue: ------ When printing the reports which are Print Check(Top, Middle and Bottom), the address of that particular report is not being formatted properly which makes the printed report poor formatted/ugly. There are three types/formats of report which are Print Check(Top, Middle and Bottom) none of them are getting printed properly(address). View Ref: [Link](https://github.com/odoo/enterprise/blob/saas-17.4/l10n_us_check_printing/report/print_check.xml#L17) **Note:** Not the blank reports like Print Blank Check(Top, Middle and Bottom). Solution: ----------- Add an adequate width to the addresses class i.e; `ckus_payee_addr`. Steps to reproduce:- -------------------- 1. Create a demo db in version 18.0 with `l10n_us_check_printing` module installed. 2. Create a payment record and confirm it. 3. Try printing that payment with any of (top/middle/bottom) Print Check reports. 4. check with the address which would've broken. Reference Screenshots: **Without Fix:**  **With Fix:**  OPW - 4454079 UPG - 2408700