Daily updates from Odoo
Monday, August 20, 2018
9 changes · master
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