Daily updates from Odoo
Wednesday, May 29, 2019
4 changes
Resolved issues and error corrections
This fixes a Point of Sale configuration issue where pricelist checks could fail while settings were being edited. The change helps ensure the system uses the real saved pricelist records, reducing errors or incorrect validation when updating POS settings.
Original PR description
Since ORM changes, the ids a many2many are new (virtual) ones in a onchange, so we have to point to origin which are the real records to check that the many2one is in as it has a real id. 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 update adjusts manufacturing work order planning checks to allow a tiny one-second timing difference. It helps prevent false test failures without changing how users plan or run manufacturing operations.
Original PR description
This commit relax, by one second, two datetimes comparison regarding workorder planning to avoid any false positives 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 fix prevents an error when users create a recurring calendar event with zero repetitions or a zero interval. Instead of showing a technical crash, the calendar now warns the user so they can correct the meeting setup before saving.
Original PR description
Description of the issue/feature this PR addresses: - Task - https://www.odoo.com/web#id=1930809&action=327&model=project.task&view_type=form&menu_id=4720 - Pad - https://pad.odoo.com/p/r.5babc87865194c859bf878c22233714c Current behavior before PR: - Getting the traceback while saving the recurrent event and number of repetations as 0 Desired behavior after PR is merged: - User will be warned if he tries to save the event with 0 as the number of repetations -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Updated the tooltip for the minimum stock quantity field so it accurately reflects how reordering rules work. This reduces confusion for users setting inventory thresholds, especially when stock equals the minimum quantity.
Original PR description
Reported by a learning partner, apparently the field description didn't match the behavior. I guess the behavior is ok but only the field help should be reviewed. I tested this on runbot and it indeed triggers the reordering point if equals to the min stock rule 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