Daily updates from Odoo
Navigate
Branch
Monday, August 20, 2018
22 changes
Enhancements to existing features
This update replaces a direct database operation with Odoo's standard data access approach in the conversion tooling. It helps keep the code easier to maintain and better aligned with platform practices, with no expected change for end users.
Original PR description
Hi @odony, don't need SQL execute here, use ORM instead :-) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now swipe left or right in form views to move to the previous or next record. This makes browsing records easier on mobile devices, where the existing navigation arrows are harder to reach.
Original PR description
TASK :- https://www.odoo.com/web#id=34727&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 PAD:- https://pad.odoo.com/p/r.98b6bfa3f719a562a5c639a3a17957cc
The mail activity interface was cleaned up to reduce duplicated logic and make activity feedback easier to maintain. Added test coverage helps ensure activity and chatter behavior remains reliable for users.
Next activities can now only be updated by the assigned user or the person who created them. This helps prevent colleagues from accidentally changing someone else’s planned work, while still allowing human updates to automated activities when needed.
Original PR description
Only the assigned user and the creator of the next activity can update it. Task: 1856417
Odoo now uses the open-source Chromium browser by default instead of relying on Google Chrome. Organizations can still choose Google Chrome through configuration if they prefer, improving licensing flexibility and deployment control.
Original PR description
Current behavior before PR: https://github.com/odoo/odoo/pull/25991 introduced for the 1st time a closed source hardcoded dependency in Odoo. I'm not sure it's even legal for a LGPL project, but in any case, it makes not much sense to introduce that problem when there is the almost-completely binary compatible Chromium project, which is fully open source. Desired behavior after PR is merged: * Use by default the open source version Chromium. * Allow to configure it through CLI and conf file, for those that still want to test with Google Chrome. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa
Batch pickings can now be arranged in a chosen order before work begins. This helps warehouse teams plan more efficient picking routes and manage larger batches without relying on paper-based sequencing.
Original PR description
- [x] Manual QA on runbot
A batch picking should give the possibility to order the pickings to be done.
Common use cases are:
- Accomodate pickings for efficiency
- Accomodate delivery routes ("delivery route" = "picking batch")
**Description of the issue/feature this PR addresses:**
- Pickings cannot be manually ordered within a picking batch (eg. optimized for efficiency)
**Current behavior before PR:**
- If I want to order a picking batch I ad to do so manually on paper
- If it's a long batch with several sheets, this became almost in-manageable
**Desired behavior after PR is merged:**
- I can pre-order the pibkings in the order they should be executed
**Note:** Please do not close, even if not immediately accepted (wishlist tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
@xoe-labsThis update improves the wording and setup rules around manufacturing work centers, work orders, and productivity losses. Users get clearer labels and fewer confusing configuration choices, helping teams record productivity issues more consistently.
Original PR description
Description of the issue/feature this PR addresses: Task : https://www.odoo.com/web#id=58625&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.4ae013c740b2bb664774e536a69e3772 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 update makes several inventory and manufacturing screens clearer and safer to use. It moves required information into more visible places, limits scrap actions to appropriate product types, improves lot creation feedback, and sets practical defaults to reduce data entry errors.
Original PR description
task : https://www.odoo.com/web?#id=1838954&action=327&model=project.task&view_type=form&menu_id=4720 pad : https://pad.odoo.com/p/r.43fb5f6b2d110a41709cae7ed76bd620
This update adjusts mobile dropdown menu styling so status-related options display correctly and consistently. It also updates automated tests to help prevent the issue from returning in future releases.
Original PR description
BS4: statusbar dropdown issue https://drive.google.com/file/d/12smrfCMGo4iH2FqPaGCxphu5ltEax7XX/view?usp=sharing https://drive.google.com/file/d/1NqBMNOKOOKk8vl6dMbFduBCuWew94VEw/view?usp=drivesdk
Resolved issues and error corrections
Fleet reference data has been moved from demo-only content into standard module data. This ensures the fleet module has the needed baseline information even when a database is created without demo data, improving consistency for real use cases.
Original PR description
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 fixes a visual alignment issue in the web interface where menu entries without sub-items did not line up properly with other entries. The change makes navigation menus look more consistent and easier to scan for users.
Original PR description
fix alignment of menu entries without children: https://drive.google.com/a/odoo.com/file/d/10_j3cFgOJ5tpUWNpN1vYJDyKbuGvxefK/view?usp=drivesdk 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 fixes the color picker used for tags on forms so it appears where users expect when changing a tag color. The change improves usability and reduces confusion when editing tagged records.
Original PR description
BS4 Issue: The color change box is not appearing at the desired location when u try to set the color of a tag ( https://youtu.be/H5lUiKIVrsU ) 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
The checkout payment page has been cleaned up to make payment methods, billing and shipping details, and delivery options easier to read and compare. This improves the shopping experience by fixing alignment issues, reducing visual clutter, and making labels such as free delivery clearer.
Original PR description
- align payment method(Ex.Stripe) form attributes in row. - fix align between radio button and payment method name. - removed header div from 'billing & shipping'. - set badges(Ex.free) and align between badges and delivery method name in choose delivery method. - border subtraction from delivery methods div as already card class has border. Description of the issue/feature this PR addresses: 1) https://drive.google.com/file/d/1fZje7_eSA9H3E4wJ35jYTkQohU5NkVg1/view 2) https://www.awesomescreenshot.com/image/3517534/d56b76dbef078ad172f73d976bcbca82 Current behavior before PR: UI issues in shop/payment page in website. Desired behavior after PR is merged: Improved ui of shop/payment page. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Opening the Employees app could fail when the Time Off module was installed because leave dates were handled in the wrong format. This fix ensures leave status dates are processed correctly, allowing users to access employee records without interruption.
Original PR description
Click on the employee app causes a traceback when hr_holidays is installed. With this commit, leave_date_from and leave_date_to receive a date as expected instead of a datetime when computing the leave status. 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 fixes a visual issue where statusbar dropdowns could appear or behave incorrectly in forms. The change improves usability for users working with records that rely on status changes, making navigation and updates more reliable.
Original PR description
BS4: statusbar dropdown issue https://drive.google.com/file/d/12smrfCMGo4iH2FqPaGCxphu5ltEax7XX/view?usp=sharing https://drive.google.com/file/d/1NqBMNOKOOKk8vl6dMbFduBCuWew94VEw/view?usp=drivesdk -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix adjusts portal page layouts across several Odoo apps so they render properly on tablet-sized screens. It improves the experience for customers and users viewing documents, projects, purchases, sales, or partner information through the portal.
Original PR description
BS4 issue in pad: https://drive.google.com/file/d/11nTNXy5IWSLghD_jIteNRiOOqcWF0oDb/view?usp=drivesdk expected https://drive.google.com/file/d/1TTF4fyrBFriI_N0qyFWoRASnPGaW-3Jr/view?usp=drivesdk 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
The Timesheets & Forecast Analysis report no longer crashes when opened. The report grouping options were adjusted so users can still analyze timesheet and forecast data in flexible combinations without hitting an error.
Original PR description
Before this - Unable to see the 'Timesheet and Forecast Analysis' report. In this commit - Traceback in because now system is not supporting the multiple fields given for groupby in list. Hence for now removed the list of multiple fields and provided the single field for groupby. This commit is related to bug#1871683 .
Odoo Sign now avoids sending duplicate or unnecessary email notifications during signing, completion, copy sending, and resend flows. This reduces inbox noise while keeping signers and followers informed, and also improves related actions such as previewing requests and downloading completed documents.
Inventory adjustments processed through barcode scanning now use the correct validation flow, preventing tracebacks during validation. Products that require lot or serial tracking also require that information when entered manually, helping avoid invalid inventory adjustments.
Original PR description
… to validate barcode. Now action_done is private method as '_action_done' and it is called from method 'action_validate' to validate barcode. Related to Issue: 1868792 While validating barcode it gives traceback. https://drive.google.com/file/d/1CxcLGDlkj4gvxMXPu4ovKITAG_xuGLvP Issue : https://www.odoo.com/web#id=1868792&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.4ca6f223a67f35402db23a780d7c7b5d
This fixes a layout problem affecting customer portal pages on tablet-sized screens. Helpdesk and subscription portal content should now appear as intended, improving readability and usability for customers using those pages.
Original PR description
BS4 issue in pad: https://drive.google.com/file/d/11nTNXy5IWSLghD_jIteNRiOOqcWF0oDb/view?usp=drivesdk expected https://drive.google.com/file/d/1TTF4fyrBFriI_N0qyFWoRASnPGaW-3Jr/view?usp=drivesdk
The signing process no longer assumes an SMS number is always provided when creating a signature request. This prevents errors in flows such as salary contract handling and avoids unnecessary updates to contact records.
Original PR description
The sms_number is a related, not mandatory field on a sign.request In hr_contract_salary for instance, the sms_number is not given (KeyError). In the wizard it was given but just the value of related. This was making an unecessary write on the partner when the key was given.
Documentation and clarification updates
The corporate Contributor License Agreement record for Dynapps N.V. has been updated. This keeps Odoo's contributor legal documentation current and helps ensure contributions are properly covered.
Original PR description
Update of DynApps N.V. corporate CLA agreement. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr