Daily updates from Odoo
Wednesday, May 29, 2019
11 changes · master
Enhancements to existing features
The portal wording for invoices and bills has been clarified so customers can better understand what they are viewing. This reduces confusion in the customer portal and makes financial documents easier to identify.
Website themes can now reference default image records used by snippets, making it easier to replace or customize those images consistently. This helps theme designers deliver tailored website visuals with less manual work and fewer duplicated changes.
Original PR description
…customize the default ones easily Description of the issue/feature this PR addresses: * Task: https://www.odoo.com/web#id=40913&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 * Pad: https://pad.odoo.com/p/r.988d02bb3aaadcfdc7877bd8db614794 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 removes an unused internal variable that was triggering a code quality warning. The application behavior remains the same, but the codebase is cleaner and easier to maintain.
Original PR description
Description of the issue/feature this PR addresses: Fix lint error. Current behavior before PR: Works fine, but has lint error. Desired behavior after PR is merged: Works in the same way, but hasn't lint error. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update renames internal company references to better match how users and the system already understand company information. It improves consistency across accounting-related features and reduces confusion for future maintenance, with little expected impact on day-to-day users.
Original PR description
The goal is to be coherent with the user property. Actually, company_id and company_ids on the environment are no fields. Calling env.company_id returns a browse record, not an id.
The project overview now includes a clearer section title for the timesheet-related table. This makes the overview easier to understand when reviewing project time, forecasts, and sales information.
Original PR description
In order to make the project overview more understandable, we introduces sections in the bottom table. project_timesheet_forecast_sale intends to add a new section, thus a new section tittle. This is done through view inheritance related task #1968121
Mobile status indicators now appear gray when they cannot be changed. This helps users quickly understand which statuses are informational only and avoids confusion when tapping unavailable options.
Original PR description
…t clickable so user can easily understand it's not changeable * Task: https://www.odoo.com/web?#id=35306&view_type=form&model=project.task&action=327&menu_id=4720 * Pad: https://pad.odoo.com/p/r.a14e26f2115039e6abf3b3c009be432e
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
Documentation and clarification updates
This pull request records the signed corporate licence agreement for IvyWeb (Pty. Ltd.). It is an administrative legal update that helps confirm contribution rights and does not change Odoo product features or user workflows.
Original PR description
This is the corporate licence agreement for IvyWeb (Pty. Ltd.) 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