Wednesday, July 3, 2024
9 changes · 17.0
Resolved issues and error corrections
This fixes an error that occurred when users created more than one maintenance request at the same time. Each request now gets its activity note correctly, helping teams process maintenance work without interruptions.
Original PR description
Description of the issue/feature this PR addresses:
call to _get_activity_note should be request not self
Current behavior before PR:
When creating more than one maintenance you get the error:
"raise ValueError("Expected singleton: %s" % self)" on
note = self._get_activity_note()
Desired behavior after PR is merged:
create the note for each request correctly
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prLeave records that have been archived are now excluded from relevant leave reports in Odoo 17.0. This keeps reporting totals accurate by preventing inactive leave entries from appearing in business reports.
Original PR description
In 17.0, some reports would not exclude archived leaves. This is specific to that version, as the active field is replaced by a "cancel" state in further versions.
Sales orders in the Italian Declaration of Intent flow no longer fail when a customer or related record has no country code. The check now safely treats missing country information as not matching, preventing avoidable errors in sales processing.
Original PR description
Currently a country code check on SOs may fail in case there is no country code. After this commit the check will return `False` in case there is no country code. (no task) see e.g.: https://runbot.odoo.com/runbot/build/64900406
This fix prevents confusing database failures when users group records by a property field linked to an invalid or missing model. Instead of producing an unsupported query in newer PostgreSQL versions, Odoo now shows a clear user-facing error so the configuration issue can be corrected.
Original PR description
In PostgreSQL 16, we can no longer order by the constant FALSE anymore ("ERROR: non-integer constant in ORDER BY"). But the ORM can generate this `ORDER BY FALSE` (and `GROUP BY FALSE`) clause if we group by a property field linked to an invalid (transient/abstract) or non-existent model. Instead of making no sense query, raise a UserError to indicate the problem.Delivery slips now display customer references, incoterms, tracking details, and shipping information across better-sized areas instead of crowding too much text onto one line. This makes printed delivery documents easier to read and helps avoid missing or unclear shipment details.
Original PR description
Steps to reproduce: - Create a sale order with customer ref and incoterms set - Add Shipping and confirm - On the picking manually set the tracking ref and print Bug: 1- no max width on (customer ref/incoterms) 2- too much info on a single line Fix: set max-width and break the data on two line if too many collumns opw-3892680
This update improves an internal diagnostic tool so important troubleshooting information is less likely to be hidden by logging settings. It also ensures timing details are shown consistently, helping support teams investigate issues more accurately.
Original PR description
Small fix and improvement on dumpstack function
Upsell quotations for subscriptions now show prorated discount notes only when at least one product is actually discounted. Discounted products are marked with an asterisk so customers and sales teams can more easily understand which subscription items are affected.
Original PR description
Before this commit, prorata discount description is added when upsell of subscription is created even if there is any product discounted or not. After this commit, prorata discount description is added if there is any discounted product when upsell is created. add (*) as a suffix on product's description if product is discounted. change prorata discount description to show user discounted products on subscription. task-3859792
This update resolves a visual issue in the Sign app where the 'Sign Now' button was causing unwanted spacing in the breadcrumb navigation when users zoomed in on the sign template view. A CSS styling adjustment ensures the button no longer breaks the text layout, providing a cleaner and more professional appearance.
Original PR description
**Version:** - saas-16.3 **Step to reproduce:** - In the sign app, open the sign template iframe view. - When zooming in, the 'Sign Now' button breaks the text and creates extra space in the breadcrumb. **Issue:** Currently, the sign now button text creates extra spacing. **Solution:** Add the CSS class so that it will not create additional spacing task-3977792 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix removes a duplicate display of the planned date field that was appearing twice when viewing tasks in the customer portal. The issue was caused by an xpath being added twice in the template, and removing the duplicate ensures a cleaner, less confusing user experience when checking task details.
Original PR description
Steps: - Install Website and Project module - Open the Project module - Open any project's task - Set the Planned date - Now go to the Website module - Go to My Account - Open Tasks - Open any my task Issue: - When we open any my task in portal , there is planned date show twice time . Cause: - Added xpath twice time. Fix: - remove an xpath from the portal my tasks. task-3610485