Daily updates from Odoo
Monday, January 13, 2025
9 changes
4 changes
Enhancements to existing features
This update simplifies how automated tests enter a special test mode, making the test code easier to maintain. It affects several accounting, reporting, localization, and WhatsApp test areas, with no expected change for everyday users.
Original PR description
Use the context-manager to simplify test code. odoo/odoo#193348
The quick search menu in the search bar now opens using a more robust dropdown behavior, helping it appear correctly even when users work inside pop-ups or overlays. This improves day-to-day usability and reduces cases where search options are hidden or difficult to access.
Original PR description
This commit makes it so the search_bar quick search uses the Dropdown component, this fixes issues where the menu would sometimes be under overlays such as modals. See community PR: https://github.com/odoo/odoo/pull/190352
Shop floor teams can now choose whether the final work order closes the manufacturing order directly. This reduces extra clicks for teams that usually close orders right away, while letting others keep a manual closing step to match their process.
Original PR description
Currently, in the shop floor, when marking the last WO of an MO as done, there is the option to also close the MO. This requires users who want to close the MO to press two buttons in different places. For users who don't want to close the MO, this can also lead to confusion whether they marked the WO as done or not. To improve the user experience, we introduce a new option: 'Close Manufacturing Order' which allows the desired shop floor WO close behavior to be set in the operation type settings. When enabled (default), the mark as done button on the last WO of an MO in the shop floor will have a 'Close Production' button directly instead of a 'Mark as Done' button. When disabled, the MO needs to be closed manually after marking the last workorder as done, as we now no longer show the Close production button on the workorder after marking it as done. task-4367540
Scanning a packaging barcode from the barcode app homepage now works like scanning the product barcode, making it easier to find items without opening packaging. Inventory counting behavior is unchanged, so packaging scans during inventory still add the correct packaged quantity.
Original PR description
Normally, scanning the barcode of a product packaging has no effect on the barcode module homepage. For the convenience of not having to open the packaging in order to scan the barcode of the product it contains just to locate it, the barcode on the packaging itself is now treated the same way as the barcode on the product itself when scanned on the module homepage. The behaviour with inventory taking (ie adding the product as many times as the packaging contains) remains unchanged. Task ID: [4284938](https://www.odoo.com/odoo/project/966/tasks/4284938)
5 changes
Enhancements to existing features
Searching email templates by category has been optimized so it no longer slows down when there are many templates. This improves responsiveness for databases with large numbers of email templates, reducing searches from several seconds to near-instant in benchmark testing.
Original PR description
When we have thousands of mail.templates, the search was taking seconds. The previous code was searching on every template, computing the `template_category` and then filtering those records to make the domain. Benchmarks done _au-doigt-mouillé_ : with 60k templates, the test was running in 4 seconds and is now running in 0.02 on a reliable test server (aka “my laptop”)
Automation rules now keep their existing filters when trigger fields are edited, reducing the risk of unexpected automation behavior. When a filter is changed, the related trigger fields are updated automatically, making automation setup more reliable for save and UI-change triggers.
Original PR description
Backport of 105e313775a6853d8dcd8ea89af7f710f4e1e2a1 **Purpose** Currently, editing any trigger field of an automation erases the domain, which may lead to unexpected behavior as some "light" automations (i.e. in CRM) hide their domains (for user friendliness). After this commit, any change in the trigger fields won't erase the domain. Also, any change in the domain will update the trigger fields. This is true for: `On save` and `On UI change` triggers. opw-4367901
This change updates the US check printing app to avoid issues in automated validation environments. It helps keep internal quality checks running smoothly without changing day-to-day business workflows.
Original PR description
Task 47452
Documents users can now create server actions and automation rules directly from the cog menu, making it faster to configure document workflows for selected folders. Menu labels and controls were also clarified so business users can more easily find and manage available actions.
Original PR description
Server Actions =========== - Rename Action menu to "Actions on select" - Add an Actions creation in Actions menu (cog wheel) - Redirect to Server Actions Automations ========== - Add an Automations menu in Documents Cog Menu, below Actions on select - If base_automations is not installed -> propose to upgrade to Studio - If base_automations is installed -> redirect to Automations rules lighten as in CRM In the context of providing a partially pre-filled automation rule form for the target folder, we change the `folder_id` label from "Parent folder" to "Folder". task-4334749
Subscription sales orders that require customer payment but do not have a saved payment method now show a clear status indicator. This helps teams quickly identify orders waiting for customer action before invoices can be created automatically.
Original PR description
When a subscription has the require_payment payment flag and no payment token, we will send a reminder to pay by mail. No automatic invoice will be created. Before this commit, when the SO is in this situation, no visual aid will help. taskid: 4367794