Daily updates from Odoo
Thursday, May 9, 2019
5 changes · master
Enhancements to existing features
This update cleans up several Helpdesk-related integrations after recent feature work, making the code easier to maintain and more aligned with internal guidelines. It also improves how repair counts and sales order links are handled, reducing unnecessary processing while preserving existing user behavior.
Original PR description
Task 1909413 has been merged, providing lots of news feature from a helpdesk.ticket. However, some part of the code is not clean enough. This task aims to clean it, to make it fit guidelines, and to avoid bad practises. * cleaning of domain creation in helpdesk_sale * optimization of compute method in helpdesk_repair * renaming of methods to fit guidelines in several modules Task-1909413
Dashboard-related add-ons now install only when their business features need them, instead of automatically enabling the dashboard module by default. This reduces unnecessary installations while keeping dashboards available when dependent apps are used.
Original PR description
Dependents should auto_install regardless of web_dashboard being installed or not, forcing its installation in the latter case. cf odoo/odoo#29431 for technical part
Resolved issues and error corrections
The Mail activity view now keeps its first column at a consistent width. This prevents the table layout from shifting when users change filters or domains, making the screen easier to read and less distracting.
Original PR description
The first column should have a fixed width to avoid the table to resize when changing the domain for example. Task 1894990 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
Code cleanup and technical improvements
Invoice payments are now handled through a clearer shared registration flow, reducing duplicated logic in accounting screens. This should make payment-related behavior easier to maintain while keeping the business workflow largely unchanged for users.
Original PR description
Task 1903572 purpose: always use the transient model when registering the payemtn from invoice (single or multi) to clean some code and make things more clear specs: need to see if there are real benefits of doing so -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoice payments are now registered through a dedicated temporary workflow, whether paying one invoice or several at once. This simplifies the payment process internally and should make future maintenance of payment-related features more reliable across affected accounting localizations.
Original PR description
Task 1903572
purpose:
always use the transient model when registering the payemtn from invoice (single or multi) to clean some code and make things more clear
specs:
need to see if there are real benefits of doing so