Daily updates from Odoo
Wednesday, August 22, 2018
7 changes
Enhancements to existing features
Inventory adjustment lines now stay limited to the product chosen for the adjustment. This prevents users from accidentally counting or updating a different product, improving accuracy during stock checks.
Original PR description
Pad:https://pad.odoo.com/p/r.ee3732b1873154647589c53ef755dc95 Task:https://www.odoo.com/web#id=1861241&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 purpose: When I create an inventory adjustment and select an inventoried product, I should then only be able to select that product in the inventory details lines. before this commit, I select the inventoried product (set by default,editable when adding a new line) after this commit, I should only be able to select the inventoried product (set by default, readonly when adding a new line) Closes: # Task: 1861241 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
Sales and profitability reports now load faster when orders involve multiple currencies and exchange rates. The change stores the relevant exchange rate directly on each sales and point-of-sale order, reducing the work needed to build reports.
Original PR description
This speed up a lot reports like sale.report when multiple currencies with multiple rates are used, even with few currencies and few rates. 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
Product quantity values now load much faster in large stock databases by avoiding unnecessary stock move records during calculation. This improves screen loading times for inventory-heavy businesses, especially where many historical stock moves are completed or cancelled.
Original PR description
Description of the issue/feature this PR addresses: Quantity fields computation on products can become very slow when there are a lot of stock move in the database. I did most tests in version 8, but…
Description of the issue/feature this PR addresses: Quantity fields computation on products can become very slow when there are a lot of stock move in the database. I did most tests in version 8, but the behavior is the same in master. In a database with more than 5 million stock moves, the computation of the qty fields when loading a view with 80 products was around 4.9 seconds. After the fix, it became 0.3 seconds. On database with very few stock moves, it won't make a difference. but when there are more stock move done and cancel than waiting/assigned/confirmed, then the performance will be better. The only risk I see of this change, is if a module add a stock move state. I minimized the diff in this PR, but to we could add a hook method like `def _get_domain_move_state` to return the domain. This way, if a module adds a state on stock_move table, it could also override this method if needed. Current behavior before PR: Very slow computation of quantity fields on products Desired behavior after PR is merged: Fast computation of quantity fields on products -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The gamification app now includes improved report templates and supporting visuals for tracking goals and challenges. This makes performance reporting clearer and more useful for users managing engagement programs.
Original PR description
task: https://www.odoo.com/web#id=30824&view_type=form&model=project.task&menu_id=5200 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Records created from incoming emails can now automatically create or link the sender as a contact and subscribe them to future replies. This helps ensure applicants, leads, and task contacts receive follow-up messages instead of being left out of the conversation.
Original PR description
Linked task : https://www.odoo.com/web#id=46151&view_type=form&model=project.task&action=333&active_id=965&menu_id=4720
Maintenance teams can now record when equipment or tools are actually put into service. Preventive maintenance schedules use this effective date to calculate the next planned maintenance, making servicing timelines more accurate.
Original PR description
- calculate next preventive maintenance according to effective date Task: https://www.odoo.com/web#action=333&active_id=131&id=33188&menu_id=4720&model=project.task&view_type=form Pad: https://pad.odoo.com/p/r.f54f7024d107dcfb92e4db5ce0bce61b 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
Maintenance planning now calculates the mean time between failures using the equipment's effective date and its first maintenance request. This improves preventive maintenance scheduling so teams can better anticipate service needs and reduce avoidable downtime.
Original PR description
…1st maintenance request Task: https://www.odoo.com/web#id=33188&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.f54f7024d107dcfb92e4db5ce0bce61b