Wednesday, June 14, 2023
4 changes · master
Enhancements to existing features
Point of Sale pricing now uses one clear price status instead of two overlapping fields. This makes price changes easier to manage across discounts, loyalty, sales orders, self-ordering, and French POS certification, reducing confusion and maintenance risk.
Original PR description
*: l10n_fr_pos_cert, pos_discount, pos_loyalty, pos_sale, pos_self_order The `Orderline` model contains the fields: `price_manually_set` and `price_automatically_set`. They are meant to signify what type of price the orderline has: `automatic`, `manual` or `original`. It's very confusing to manage the two fields when in fact they only describe three types of setting the orderline price. This PR replaces the 2 fields with a single one: `price_type`, which will take one of the 3 possible values. Task: 3358265 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Attachment image previews no longer show the file name as a hover title in normal use. This removes unnecessary technical information from the interface while keeping it available for debugging contexts.
Original PR description
This commit remove the title on the attachment image widget when not in debug mode. The title gave the name of the file and wasn't really necessary as it is rather a technical info. task 3343366
Recruiter names and job titles now stay neatly within the contact card, even when they are long. The phone icon is hidden when no phone number is available, giving job applicants a cleaner and less confusing experience.
Original PR description
Before this PR, when the recruiter's name and job position were excessively long, it extended beyond the boundaries of the box. And, if the recruiter did not have a phone number, the phone symbol would still be displayed within the box. In this PR, The name and job position of the recruiter were shortened and the space at the bottom of the recruiter's email was minimized. task-3342768
A new automated test confirms that binary fields can safely be used to control available choices in many-to-many tag fields. This helps protect an existing supported behavior used by business apps and reduces the risk of future regressions.
Original PR description
The commit only adds a test which checks that binary field can be used as the domain of many2many tags field. We already have a case in the "account" addon so the test is there to check that the feature is supported. task id: 3336189