Thursday, February 6, 2020
14 changes · master
Enhancements to existing features
Sales orders with section or note lines can now be converted to invoices without errors. These lines are clearly marked when they will be invoiced, helping users keep invoice details consistent with the original order.
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
Percentage fields now show the percent sign beside the input instead of inside it while editing. This makes data entry clearer because users edit only the numeric value, with the system handling the percentage formatting consistently.
Original PR description
before this commit: percentage symbol is part of input in edit mode percentage symbol should be outside like monetary widget. after this commit: percentage symbol will be at last after input tag percentage will be displayed in span and preceded by input tag, so user can easily edit only value, currently while editing % also comes as a value which is wrong, after this commit, percentage symbol will be displayed on right end of input tag like monetary widget shows currency symbol at last. task 2065078
When an invoice is validated, Odoo now automatically schedules follow-up activities based on the due dates of the related accounting entries. This helps sales teams notice overdue invoices sooner and supports more proactive payment collection.
Original PR description
Task 2093179 Today, there is nothing that reminds a salesperson that an invoice becomes overdue. I propose that activities get created automatically on an invoice based on the ‘due date’ of the journal items as soon as an invoice gets validated. This would greatly help the collection effort and be proactive rather than reactive. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now add existing related records in list views even when they only have permission to read those related records. This makes list-based relationship editing behave consistently with tag-based editing and reduces unnecessary access-related friction.
Original PR description
Before this commit, there was a discrepancy between many2many_tags widget and regular many2many list That is, in tag mode, when someone had read access alone on the comodel he could modify the members of the m2m relation on the current model Which couldn't be done in m2m list After this commit, it is possible in a m2m list to add records to a relation, even if we don't have CRUD access on the comodel Task 44074 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
Website theme settings such as colors, fonts, and layout are now available directly inside the website editor instead of a separate customization window. This makes design changes easier to find and manage while keeping related website editing tools in one place.
Original PR description
*: theme_bootswatch Previously, theme customization was done through a modal dialog in the website module, this was not very user friendly since the rest of the customization for the website design…
*: theme_bootswatch Previously, theme customization was done through a modal dialog in the website module, this was not very user friendly since the rest of the customization for the website design was done from edit mode, meaning the user had to exit edit mode to customize things such as theme colors or fonts. It was also rather confusing to have these seemingly related things in completely unrelated places. This commit moves all of the options that used to be in the theme customization modal into a new tab in the editor's left panel. Instead of having an entirely dedicated system for theme options, those theme options are now simple snippet options. See the customizeWebsite generic method. This allows to make any option available in the third tab or on any meaningful element like the header or the footer. This also allows to take advantage of all the features of the left panel: dependencies, visibility update, etc. Note: same as before, those changes do apply the color/size/layout immediately on the website, even if not saved. Changing that behavior is complex and might be the job of another task. See sub-commits for details task-2088298
The subscription dashboard now gives sales teams clearer revenue insights, including helpful KPI explanations, multi-salesperson views, clickable report lines, and PDF export. Subscription performance tracking is also more reliable because it is based on subscription change history rather than invoice lines, reducing misleading changes caused by currency rates or display issues.
Original PR description
Improve the behaviour of the sale subscription dashboard for salesman.
Resolved issues and error corrections
Purchase order imports now better complete required line information automatically, reducing manual cleanup for users. The related purchase reporting test was improved to ensure tax-inclusive totals are handled correctly when product taxes apply.
Original PR description
Task : https://www.odoo.com/web#id=2093205&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.28ecb10fd3035ca1024c5db52fff8978 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
### Description of the issue/feature this PR addresses: The refund wizard is not compatible with the LATAM document types. This PR try to extend the original wizard to be able to properly create credit notes and invoices ("modify" option in the wizard). There are multiples fixes so we enumerate the errors bellow, each one has their own commit ### Current behavior before PR: 1. We are not able to set Document type in the Refund wizard. 2. When selecting "modify" option in the Refund
Original PR description
### Description of the issue/feature this PR addresses: The refund wizard is not compatible with the LATAM document types. This PR try to extend the original wizard to be able to properly create…
This fix prevents an error when creating an invoice from a sales order line that has no product. Sales teams can now handle incomplete or empty sales orders more smoothly without the process failing unexpectedly.
Original PR description
Description of the issue/feature this PR addresses: Improve the behaviour of the sale subscription dashboard for salesman. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The eBay sales integration now avoids unnecessary warning messages when it is installed but not yet configured. This keeps scheduled background checks from cluttering logs, making monitoring cleaner for teams that are not actively using the integration.
Original PR description
When sale_ebay is installed but not configured, its crons are frequently raising unnecessary warnings, and polluting logs.
A small typo in a filtering rule caused the inter-company sales and purchase screen to crash in the browser. This update corrects the typo so users can open and use the affected configuration without interruption.
Original PR description
The domain operator is 'not in ' (notice the trailing space). With that trailing space, the operator is not recognized as a supported operator and the domain interpretation crashes (JS side). Domain introduced in 7570c39
### Description of the issue/feature this PR addresses:
The refund wizard is not compatible with the LATAM document types. This PR try to extend the original wizard to be able to properly create credit notes and invoices ("modify" option in the wizard).
There are multiples fixes so we enumerate the errors bellow, each one has their own commit
### Current behavior before PR:
1. We are not able to set Document type in the Refund wizard.
2. When selecting "modify" option in the Refund wizard it raise and error "can not create credit note" and do not let us to create neither the credit note. or the new invoice.
3. Credit note is been created in the default journal of the system and not in the same journal of the original invoice.
### Desired behavior after PR is merged:
1. We are able to select Document type in the Refund wizard when creating a credit note.
2. When selecting "modify" option now we can create both the credit note and the new invoice, each one now has the proper document type.
3. Credit note now is created in the same journal of the original invoice.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#44616
Forward-Port-Of: odoo/odoo#43514Because the tax closing entry is created (empty) at the creation of the CoA, it is not possible anymore to change it later, even if the user didn't create any journal entry. By checking that there are no account.move.line instead of account.move, and also there are no entries with a name different from '/' (to ensure that the sequences are untouched) we can change the CoA if needed. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior aft
Original PR description
Because the tax closing entry is created (empty) at the creation of the CoA, it is not possible anymore to change it later, even if the user didn't create any journal entry. By checking that there are no account.move.line instead of account.move, and also there are no entries with a name different from '/' (to ensure that the sequences are untouched) we can change the CoA if needed. 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 Forward-Port-Of: odoo/odoo#44647
Since commit 92737f2 (finetuning of 7b49f58) field website_id, website_tag_ids are missing from form view of res partner. Now we use a more precise xpath, hardcoding the group name into the xpath to be sure that fields are correctly added below the company_id field from a visible tab. 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.odo
Original PR description
Since commit 92737f2 (finetuning of 7b49f58) field website_id, website_tag_ids are missing from form view of res partner. Now we use a more precise xpath, hardcoding the group name into the xpath to be sure that fields are correctly added below the company_id field from a visible tab. 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 Forward-Port-Of: odoo/odoo#44120
Also make the CoA translatable -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#43768
Original PR description
Also make the CoA translatable -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#43768