Sunday, April 13, 2025
9 changes · saas-18.2
Enhancements to existing features
The Discuss and messaging areas received small visual refinements to make conversations, invitations, notifications, and menus easier to scan. These changes reduce visual clutter and better highlight the most important actions without changing how users work.
The channel invitation menu has been visually simplified so key actions like searching, selecting people, inviting, and sharing links stand out more clearly. Supporting text and invite links are now less prominent, making the menu easier and less tiring to use.
Original PR description
This menu is dense of information and user interaction, and without reducing visibility of some information this feels more exhausting than it should. This commit reduces visibility of textual info text and invite link (smaller, reduced opacity), helping highlighting the most important items: search, suggested / selected items, invite / share link buttons. Before <img width="482" alt="Screenshot 2025-04-07 at 16 30 55" src="https://github.com/user-attachments/assets/8ace7532-eb5e-426d-bc4f-d792d1923567" /> After <img width="481" alt="Screenshot 2025-04-07 at 16 31 56 1" src="https://github.com/user-attachments/assets/54780e64-37fd-4f5f-9dd4-e63fdfce0a1d" />
The messaging menu has been visually refined with better spacing between avatars and message text, tighter item padding, and clearer background contrast for less important items. This makes notifications easier to scan while keeping the change small and low-risk.
Original PR description
- more spacing between avatar and text content - less spacing between items, thanks to slightly reduced vertical padding for each item - non-important items have slight different bg compared to messaging menu
The Discuss interface has been visually refined with softer message borders, slightly smaller author names, closer spacing for grouped messages, and rounder avatars. These small polish changes make conversations feel cleaner and easier to scan without changing how users work.
Original PR description
Message style improvements: - author name is slightly smaller - squashed message are slightly closer to previous message - border around message bubble has opacity reduced Borders: - reduced/removed borders around discuss sidebar/header/panel - header thread action have border replaced by bg color Avatar - avatar are rounder (`.rounded` => `.rounded-3`) NotificationMessage - slightly reduced opacity
Resolved issues and error corrections
The Discuss command palette now shows conversation avatars at a clearer, consistent size. This makes conversations easier to recognize while keeping the palette compact and improving the visual distinction between main and secondary text.
Original PR description
Conversation avatars were smaller than in discuss and also not integer scaling from `avatar_128`. This is fixed by using 32px width/height. Also reduce padding as to not make command palette significantly bigger + reduced opacity of secondary text for better difference with main text (conversation name). Before <img width="661" alt="Screenshot 2025-04-10 at 15 02 45" src="https://github.com/user-attachments/assets/ad7a8a6c-7f72-4e9d-a26e-4f19ee127a07" /> After <img width="654" alt="Screenshot 2025-04-10 at 15 02 24" src="https://github.com/user-attachments/assets/da510fe5-6904-4096-bc3b-4cf3b74c9f28" />
Miscellaneous changes
Before this PR, Setting the on-hand quantity from the product form would correctly set the product's quantity but also reset the inventory quantity to 0. While this behavior is correct,it caused a line decoration warning to appear in the Inventory Adjustment tree view. Steps to Reproduce =================== - Create a storable, non-tracked product. - Update its quantity by clicking the "Update Quantity" button, ensuring multi-location is disabled. - Go to Inventory Adjustment and
Original PR description
Before this PR, Setting the on-hand quantity from the product form would correctly set the product's quantity but also reset the inventory quantity to 0. While this behavior is correct,it caused a…
Before this PR, Setting the on-hand quantity from the product form would correctly set the product's quantity but also reset the inventory quantity to 0. While this behavior is correct,it caused a line decoration warning to appear in the Inventory Adjustment tree view. Steps to Reproduce =================== - Create a storable, non-tracked product. - Update its quantity by clicking the "Update Quantity" button, ensuring multi-location is disabled. - Go to Inventory Adjustment and locate the newly created product. The inventory quantity is correctly set to 0, but it is highlighted with a warning. Issue ====== Although the inventory quantity is correctly set to 0, the `inventory quantity set` field is not reverted, causing the line decoration warning to appear. This commit resolves the issue by using an existing method that clears the inventory quantity and sets the `inventory quantity set` field to false. task: [4579053](https://www.odoo.com/odoo/my-tasks/4579053) Forward-Port-Of: odoo/odoo#199598
When the warehouse is set to pbm_sam, MOs are assigned the procurement group name if the move origin differs from the group_id. This causes a validation error when confirming a sales order with a client_order_ref, as MO references must be unique per company. For example, if an SO has a reference S00011 - test_client_order_ref, it differs from S00011, leading to an MO name conflict. This fix ensures that MO names are always generated using the picking type sequence instead of inheriting the pr
Original PR description
When the warehouse is set to pbm_sam, MOs are assigned the procurement group name if the move origin differs from the group_id. This causes a validation error when confirming a sales order with a…
When the warehouse is set to pbm_sam, MOs are assigned the procurement group name if the move origin differs from the group_id. This causes a validation error when confirming a sales order with a client_order_ref, as MO references must be unique per company. For example, if an SO has a reference S00011 - test_client_order_ref, it differs from S00011, leading to an MO name conflict. This fix ensures that MO names are always generated using the picking type sequence instead of inheriting the procurement group name, preventing duplicate references or incorrectly setting the MO name as the SO name. Current behavior before PR: If there is more than one sale order line with MTO products: We get a duplicate name error If there is one sale order line with an MTO product: We get a MO.name == SO.name Desired behavior after PR is merged: Both cases are resolved and the MO(s) are successfully created with the appropriate name Steps to reproduce: 1.) Install sales; inventory; manufacturing 2.) Enable multi-step routes 3.) Unarchive MTO 4.) Set warehouse manufacture steps to: Pick components, manufacture, then store products (3 steps) (manufacture_steps == 'pbm_sam') 5.) Unarchive MTO 6.) Create two storable products (enable manufacture and mto routes) 7.) Create an SO with both products 8.) Add any text to the Customer Reference on the sales order (client_order_ref) 9.) Try to confirm the SO Validation Error The operation cannot be completed: Reference must be unique per Company! --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#203823
A problem occurs when deleting a cash rounding method linked to a Point Of Sale configuration. After deleting the cash rounding, the following error message appears: “The cash rounding strategy of the point of sale Shop must be: 'Add a rounding line'.” because the rounding method is empty. The main issue arises when the cash rounding method is deleted while the POS session is open: it prevents the session from closing or modifying the cash rounding, locking the user out. Steps to reprod
Original PR description
A problem occurs when deleting a cash rounding method linked to a Point Of Sale configuration. After deleting the cash rounding, the following error message appears: “The cash rounding strategy of the point of sale Shop must be: 'Add a rounding line'.” because the rounding method is empty. The main issue arises when the cash rounding method is deleted while the POS session is open: it prevents the session from closing or modifying the cash rounding, locking the user out. Steps to reproduce: - Add a cash rounding for a POS - Open the POS session - Delete the cash rounding - Try to enter the POS - Error occurs This fix ensures that the deleted cash rounding is no longer linked to any POS configuration. opw-4651976 Forward-Port-Of: odoo/odoo#205654 Forward-Port-Of: odoo/odoo#202477
The `sale_subscription` module defines a template used on the website, but it was not marked as being a frontend module. Therefore the translations were not loaded on the website and the template was never translated. In this commit we add this module to the frontend modules, so its templates displayed on the website are properly translated. Forward-Port-Of: odoo/enterprise#83349 Forward-Port-Of: odoo/enterprise#82489
Original PR description
The `sale_subscription` module defines a template used on the website, but it was not marked as being a frontend module. Therefore the translations were not loaded on the website and the template was never translated. In this commit we add this module to the frontend modules, so its templates displayed on the website are properly translated. Forward-Port-Of: odoo/enterprise#83349 Forward-Port-Of: odoo/enterprise#82489