Friday, February 21, 2020
4 changes · master
Enhancements to existing features
Several CRM, Events, and Gamification screens now show shorter, clearer labels and wider columns so information is easier to read. Opportunity lists also focus on more useful date information by showing creation dates in a date format and removing phone details from those embedded lists.
Original PR description
PURPOSE In various views, the min width of some columns is too short for the label of the field. This task aims at fixing this by increasing some minimal widths, and relabelling some fields. SPECIFICATIONS Increase the default minimal width of Boolean field from 50px to 70px to avoid readability issue. in the inline treeview of event_ticket_ids - set string of field seats_max to 'Available' - set string of field seats_reserved to 'Reserved' - set string of field seats_unconfirmed 'Unconfirmed' - set width='105px' for each of those 3 fields In views crm.view_crm_lead2opportunity_partner_mass AND crm.view_crm_lead2opportunity_partner - in the inline treeview of opportunity_ids, drop the phone field and add a date widget on the create_date In model gamification.challenge.line - relabel 'target_goal' to 'Target' In model event.mail - relabel 'mail_sent' to 'Sent' LINKS PR #43401 Task 2166865
When multiple companies need default stock locations created, the process now handles them together instead of one by one. This improves setup efficiency without changing day-to-day inventory workflows.
Original PR description
Use the fact that `create_missing_*_location` methods supports multi recordsets. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes an outdated calendar validation that referred to a date field no longer used in Odoo. It helps keep calendar behavior aligned with the current system and avoids unnecessary checks that no longer serve a purpose.
Original PR description
Description of the issue/feature this PR addresses: Date field doesn't exist since v9, So this validation doesn't make any sense. 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 XML editor now shows the no-update warning only for standard views, not custom Studio views. This reduces unnecessary alerts for users editing views that can safely be changed through the interface.
Original PR description
PURPOSE Update warning in ace editor is displayed in all views, it should only be displayed in standard views, custom views(studio views) should not have that warning as a user can change those view from UI. SPECIFICATION Display update warning only in standard view Task 2167570