Monday, June 3, 2019
4 changes · master
Enhancements to existing features
The portal opportunity page now keeps stage labels on a single line by adjusting their placement based on available space. This makes opportunity cards cleaner and easier to read, especially when many stages are shown.
Original PR description
Description of the issue/feature this PR addresses: Portal opportunity stages Current behavior before PR: Stages are in column next to Opportunity title. When there are too many, the stages don't remain on one line --> ugly Desired behavior after PR is merged: Stages should appear on one line : under Opportunity title if element is wider than 440px, next to it if element is under said width. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo Studio users can now click the image shown at the bottom of a kanban card while editing a view. This makes it possible to remove or manage that image directly, reducing frustration when customizing kanban layouts.
Original PR description
Task: https://www.odoo.com/web?debug#id=1997542&action=327&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.8e1327f486c6f5ce42a92c84790cdf42 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
In Odoo Studio's report editor, selecting or expanding an item in the sidebar now selects the matching element in the report preview. This makes it clearer which part of the report is being edited and reduces confusion when changing report properties.
Original PR description
Task : https://www.odoo.com/web#id=1986834&action=333&active_id=1519&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.4928518afca2661d89516ae2e4e01bf5
Studio now visually dims areas where a dragged search view component cannot be dropped. This helps users understand valid placement options immediately and reduces trial and error while customizing search views.
Original PR description
Currently, when we drag a component in search view, it can not be dropped everywhere. For example, a 'filter' component can not be dropped inside 'Group by' and 'Autocompletion Fields' section. But user can not see any visual indication about which component can be dropped where. This commit indicates 'undroppable' zone by adding 'text-muted' class to such tables, as soon as the draggable component touches the view. task-1978762