Sunday, December 27, 2015
4 changes
Resolved issues and error corrections
This fix restores the intended clear error message when a related field is configured with an incompatible type. Instead of showing a technical crash during module installation, users receive a more understandable explanation of what needs to be corrected.
Original PR description
With commit https://github.com/odoo/odoo/commit/0fd773a486fbc1aeef7f00ec5eab3eaf0e4c6a9d, it will raise traceback instead of Warning because of missing UserError import. Steps to produce: Take any related field, say for example country_id field of event.event, set related='address_id.name' or any other field which is not Many2one, install event module Current behaviour: traceback i.e. global name UserError is not defined Expected: IT should give User friendlily message that Type of related field is inconsistent.
The website publish and unpublish button now displays a loading indicator while the change is being applied. This helps users understand that their action is in progress and reduces uncertainty when publishing website content.
Original PR description
Task: https://www.odoo.com/web#id=11468&view_type=form&model=project.task&action=333&active_id=131 Pad: https://pad.odoo.com/p/r.1psE5QWjSdwNPXx5
This fix ensures Kanban boards display every expected column for selection-based groupings, even when no records currently belong in some columns. It helps users keep a consistent board layout and avoid confusion caused by missing empty stages or categories.
Original PR description
Fix group_by_full for selection fields to show all columns in a Kanban view even if they are empty.
The claim reporting view now shows the correct claim stages when new stages are created and assigned. This prevents confusion from displaying unrelated CRM case stages, helping teams track claim status accurately.
Original PR description
Fix Issue : #2216 It Displays stages of crm_case_stage model instead of crm_claim_stage. Thanks rsi-odoo