Daily updates from Odoo
Friday, September 2, 2016
8 changes · master
Enhancements to existing features
This change simplifies the company profile by moving configuration options into each relevant app's Settings area. Business users get a clearer setup experience, with company-specific options still supported but managed from a more consistent location.
Original PR description
Task : https://www.odoo.com/web?#id=27812&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.ea3a82ad157ba392f03749b25c4e19ad 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
When no custom form is defined, Odoo now creates a fuller default form that includes relationship fields previously left out. Large content areas such as long text, HTML, and related-record lists also use the available page width, making training and data review easier.
Original PR description
Theses changes are useful for training when we define model before teaching the views. 1. When a model has no form defined, a default view is generated displaying all fields of the model. The one2many and many2many fields were not displayed on the form, probably for aesthetic or historical (2008) reasons. 2. one2many, many2many, text and html fields should take all space in a form view for a better rendering instead of taking only 2 col or not having the label in front the field. **To merge in 9.0: vote :tada: To merge in master: vote :heart:** Before:  Now: 
Warehouse users now receive a warning when processing a transfer that involves different source or destination locations. This helps prevent accidental stock movements and gives teams a chance to review location details before completing the operation.
Original PR description
task: https://www.odoo.com/web#id=12365&view_type=form&model=project.task&action=333&active_id=131 pad: https://pad.odoo.com/p/r.VfA7AkfvkykGUKCn
Budget reports have been updated to work with the newer reporting approach and to run more efficiently. This should make budget analysis smoother for users while removing outdated report code that is no longer needed.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=22216&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad: https://pad.odoo.com/p/r.d359debbc0ebab15039fe55e6065cc47 ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Survey date questions now use improved date widgets, making it easier and more reliable for respondents to enter dates. This improves the survey-taking experience and helps businesses collect cleaner date-based responses.
Original PR description
Task: https://www.odoo.com/web#id=22615&view_type=form&model=project.task&action=327&menu_id=4720 Pad: https://pad.odoo.com/p/r.a8df8088c9902d4aebedb95b6a9338fd
This update removes unnecessary automatic updates to fields that already come from their parent records, especially in accounting entries and expense flows. It reduces extra database work when creating or changing records, improving performance while keeping the same business behavior.
Original PR description
The field journal_id and date are both required on account.move and are stored related on account.move.line. Setting the required on the account.move.line allows to make it required in the views or for the ORM but in practice it will be same as it's required on the parent. Making it required is a performance killer as it forces to specify a value for the create which will retrigger an update on the parent move. This means that adding a line with a date value on an account.move with already 10 lines will trigger 11 updates (date of the new line -> date of the move -> date on the 10 existing lines), even if the value has not changed.
This update improves the Project app experience by simplifying task reporting, removing a problematic cumulative flow report, and making project cards and onboarding data clearer. It also adds a clearer message for Pad configuration, reducing confusion for users and avoiding errors when editing project stages or deleting columns.
Original PR description
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
Company-specific configuration options have been relocated from the company form into the settings areas of their related apps. This simplifies company records and makes it easier for users to find and manage configuration in one consistent place.
Original PR description
Task: https://www.odoo.com/web?#id=27812&view_type=form&model=project.task&menu_id=4720 Pad: https://pad.odoo.com/p/r.ea3a82ad157ba392f03749b25c4e19ad