Daily updates from Odoo
Navigate
Branch
Thursday, July 1, 2021
15 changes
New functionality added to Odoo
CRM reporting now includes a dedicated forecast view for opportunities, helping teams see expected short-term revenue based on anticipated closing dates. The enterprise update keeps forecast reports focused by hiding less relevant conversion-time measures in graph and pivot analysis.
Original PR description
### [IMP] `crm`: implement the forecast feature for opportunities
This is the enterprise part of the community commit with the same name.
#### Overview of the community commit
* Add a new submenu "Forecast" in "Reporting" for CRM
* The Forecast shows 4 views:
1. Kanban
2. Graph
3. Pivot
4. List
* Objective
Shows the short term forecast for opportunities (crm_lead) based on their
expected closing (date_deadline) and have an overview of the prorated
revenues for each period (defaults to month).
* To keep the focus on the forecast, we update some fields from measure to set
as invisible
#### What's in this commit
* For Graph and Pivot views:
- set days_to_convert from "Measures" as invisible
Task-ID: 2243913
Community PR https://github.com/odoo/odoo/pull/69380Enhancements to existing features
Users can now start chats by clicking colleague avatars directly in activity views, matching the behavior already available in other screens. This makes collaboration from Helpdesk activities faster and more consistent.
Original PR description
PURPOSE The purpose of this task is to support the many2one_avatar widget in the activity view. With this, users will be able to chat with users from their avatars in the activity view, just like they can from the formview, kanban, etc. SPECIFICATION implement support for the many2one_avatar widget in the activity view replace the user avatar by the many2one_avatar_user widget in the following activity views TASK 2554466
VoIP call activities now show a contact's mobile number when no phone number is available. When both phone and mobile numbers exist, users can see both options, making it easier to reach customers through the best available number.
Original PR description
Currently call activity only uses phone number of the related partner. After this commit, mobile number will be used if phone number is not existing, or both mobile and phone number will be presented if they are both existing. task id: 2528865
Resolved issues and error corrections
The helpdesk ticket confirmation page now displays its message and icon correctly aligned after a website form submission. This improves the customer-facing experience by making the thank-you page look cleaner and more professional.
Original PR description
Currently when go to helpdesk > configuration > helpdesk team >> enable the 'website form' feature, go on the webpage and submit a ticket then the Thanks page text is not correctly aligned/centered with icon. so in this commit align the text and icon correctly in thanks page. Task-Id: 2558848
The Google Maps link from map views now sends only real route points, so users no longer need to manually remove a blank final stop before directions work. This makes route viewing smoother and avoids confusion when opening directions from Odoo.
Original PR description
PURPOSE Currently, when using the 'view in google maps' feature with routing enabled (with mapbox), the last 'empty' google maps routing point needs to be manually removed for the routing to be computed SPEC We should not get this last 'empty' routing point when redirecting to google maps TASK 2237634
Code cleanup and technical improvements
Tax details for electronic invoicing are now calculated through a shared method and grouped more consistently. This helps reduce inconsistencies across country-specific EDI flows, especially for Mexico and Peru, while keeping the change mostly internal.
Miscellaneous changes
In 14.0 when creating a Mexican CFDI, signing it, and then printing it, certain columns cannot span on multiple lines, and are thus forcing other columns to span on way too many lines to preserve horizontal space. With this commit, the classes of the columns that cannot span are updated to match those of standard columns, resulting in a balanced layout. opw-2524425 Forward-Port-Of: odoo/enterprise#19295
Original PR description
In 14.0 when creating a Mexican CFDI, signing it, and then printing it, certain columns cannot span on multiple lines, and are thus forcing other columns to span on way too many lines to preserve horizontal space. With this commit, the classes of the columns that cannot span are updated to match those of standard columns, resulting in a balanced layout. opw-2524425 Forward-Port-Of: odoo/enterprise#19295
Forward-Port-Of: odoo/enterprise#19298
Original PR description
Forward-Port-Of: odoo/enterprise#19298
PURPOSE Keyboard navigation on home menu apps with Right/Left arrow key should be smooth. SPEC When keyboard navigation done set focus to o_focused element i.e. currently selected element on patched method. TASK 2508031 Forward-Port-Of: odoo/enterprise#17820
Original PR description
PURPOSE Keyboard navigation on home menu apps with Right/Left arrow key should be smooth. SPEC When keyboard navigation done set focus to o_focused element i.e. currently selected element on patched method. TASK 2508031 Forward-Port-Of: odoo/enterprise#17820
In 14.0 when toggling between different cell values in a timesheet grid which is configured to work with days instead of hours, the cycling (0 -> 0.5 -> 1) would not work in languages other than English, because they use a comma as decimal point instead of a dot. With this commit, the cycling values (0 -> 0.5 -> 1) are not changed depending on the localization, which means the dot is never deleted or replaced with a comma. opw-2494212 Forward-Port-Of: odoo/enterprise#19310
Original PR description
In 14.0 when toggling between different cell values in a timesheet grid which is configured to work with days instead of hours, the cycling (0 -> 0.5 -> 1) would not work in languages other than English, because they use a comma as decimal point instead of a dot. With this commit, the cycling values (0 -> 0.5 -> 1) are not changed depending on the localization, which means the dot is never deleted or replaced with a comma. opw-2494212 Forward-Port-Of: odoo/enterprise#19310
Fixes a wrong comparison since 189135d7667e4869fc45e3cfa9844a718fc537e4 Forward-Port-Of: odoo/enterprise#19370
Original PR description
Fixes a wrong comparison since 189135d7667e4869fc45e3cfa9844a718fc537e4 Forward-Port-Of: odoo/enterprise#19370
When we fetch accounts from Odoo Fin proxy, there is 3 possibilities: 1. The fetched account is a new account, we create it. 2. The fetched account no longer exists in the client db, we delete it. 3. The fetched account is an existing account, we pop it from the dict. The last possibility could be problematic if the account changes (`account_data` is changed). To remedy this, we update `account_data` if the account already exists in the client db. Forward-Port-Of: odoo/enterprise#19303
Original PR description
When we fetch accounts from Odoo Fin proxy, there is 3 possibilities: 1. The fetched account is a new account, we create it. 2. The fetched account no longer exists in the client db, we delete it. 3. The fetched account is an existing account, we pop it from the dict. The last possibility could be problematic if the account changes (`account_data` is changed). To remedy this, we update `account_data` if the account already exists in the client db. Forward-Port-Of: odoo/enterprise#19303
MessageIsHtml options is allowing passing an html message in notification. Task-ID: 2557809 Forward-Port-Of: odoo/enterprise#18928
Original PR description
MessageIsHtml options is allowing passing an html message in notification. Task-ID: 2557809 Forward-Port-Of: odoo/enterprise#18928
… Mexican Peso Before this commit, the rate was only computed if the invoice's currency was different than the company's one which is incorrect because some Mexican company have USD as currency, and the rate should be set in cfdi whenever the currency is different from Mexican Peso. Forward-Port-Of: odoo/enterprise#19342 Forward-Port-Of: odoo/enterprise#19245
Original PR description
… Mexican Peso Before this commit, the rate was only computed if the invoice's currency was different than the company's one which is incorrect because some Mexican company have USD as currency, and the rate should be set in cfdi whenever the currency is different from Mexican Peso. Forward-Port-Of: odoo/enterprise#19342 Forward-Port-Of: odoo/enterprise#19245
Before this commit the text is not correctly aligned/centered. After this commit the text is correctly align/center. LINKS PR: #18846 Task-Id: 2558848 Forward-Port-Of: odoo/enterprise#18846
Original PR description
Before this commit the text is not correctly aligned/centered. After this commit the text is correctly align/center. LINKS PR: #18846 Task-Id: 2558848 Forward-Port-Of: odoo/enterprise#18846