Monday, March 23, 2020
14 changes · master
New functionality added to Odoo
Sales teams can now create CRM leads directly from eligible Facebook and Twitter posts or comments in the Social app. This reduces manual copying and helps turn social media engagement into trackable sales opportunities, while avoiding leads from the company’s own account activity.
Sales teams can now create rental quotations directly from CRM opportunities. When rental products are included, the system prioritizes creating a rental quotation, helping teams move from lead to rental order more smoothly.
Original PR description
Pad:https://pad.odoo.com/p/r.0a4ea96473d8b7c0d8be400183bf5c60 Task:https://www.odoo.com/web#id=2081209&action=333&active_id=1364&model=project.task&view_type=form&menu_id=4720
Enhancements to existing features
Pivot reports no longer offer the color index as a measure in affected apps. This removes a confusing, non-business value from reporting choices so users can focus on meaningful metrics.
Original PR description
PURPOSE In several models(helpdesk.ticket), the 'color index' field shows up in the pivot measures, Which makes sense since it is a stored integer field, but it is 'functionally irrelevant'. SPEC Remove color field from pivot measures TASK 2153090
Resolved issues and error corrections
This update keeps the Asset and Budget apps compatible with recent platform changes by replacing an outdated internal method. It helps prevent future issues during upgrades without changing day-to-day user workflows.
Original PR description
Adapt the code to use BaseModel.new instead of the (now) deprecated resolve_2many_commands
Miscellaneous changes
The various email bodies of an appraisal should be translatable. opw-2212639 Forward-Port-Of: odoo/enterprise#9432 Forward-Port-Of: odoo/enterprise#9425
Original PR description
The various email bodies of an appraisal should be translatable. opw-2212639 Forward-Port-Of: odoo/enterprise#9432 Forward-Port-Of: odoo/enterprise#9425
User selection fields on internal business records now show only internal staff users, reducing the chance of accidentally assigning portal users. This also keeps long user lists cleaner and can improve performance when selecting responsible people across many apps.
Original PR description
PURPOSE Make sure internal many2xxx fields to res.users are restricted to internal users. This is to prevent users from setting portal users on internal documents by mistake, and preventing noise and…
PURPOSE
Make sure internal many2xxx fields to res.users are restricted to internal users.
This is to prevent users from setting portal users on internal documents by mistake, and preventing noise and performance issues resulting from loading all the portal users
in those fields.
SPECIFICATION
always set the domain in the formview of the model
do NOT set the domain on the field itself
Set domain="[('share','=',False)]" on the following fields:
salesperson on res.partner
salesperson on crm.lead
crm team member
salesperson on crm.iap.lead.mining.request
salesperson on crm.reveal.rule
responsible on mailing.mailing
responsible on utm.campaign
responsible on event.event
responsible on event.track
salesperson on sale.order
salesperson on sale.subscription
related user on hr.employee
responsible on hr.job
responsible and referred by user on hr.applicant
responsible on hr.leave.type
request owner on approval.request
approvers on approval.category
manager on fleet.vehicle
responsible on product.template
purchase representative on purchase.order
same on purchase.requisition
responsible on stock.picking
responsible on mrp.production
responsible on repair.order
responsible on quality.alert
responsible on mrp.eco
team members on maintenance.team
technician on maintenance.equipment
responsible on maintenance.equipment.category
responsible on slide.channel
responsible on helpdesk.ticket
project manager on project.project
assigned to on project.task
manager on hr.expense.sheet
salesperson on account.move
responsible on crossovered.budget
notify users on data_merge.model
default user on mail.activity.type
responsible on lunch.supplier
LINKS
PR: #9204
TaskID: 2172779The data merge feature for CRM has been updated to use the renamed and relocated tag system now shared with sales teams. This keeps tag handling consistent when merging CRM-related records and helps avoid disruption after the underlying tag change.
Original PR description
As the model crm.lead.tag has been moved from crm to sales_team module, and renamed to crm.tag, the data_merge_crm app has been updated accordingly.
Updates the US English wording used for an asset depreciation method to make it clearer for users. This helps finance teams better understand the depreciation option they are selecting without changing the underlying accounting behavior.
Quality teams can now schedule follow-up activities directly on Quality Checks, ensuring issues or inspections are tracked properly. This fixes a missing activity option and corrects a related product field reference so the quality workflow works as expected.
Original PR description
It should be possible to schedule an activity on a Quality Check. opw-2222824
This updates wording in accounting reports to use “quarter” instead of “trimester” where the business meaning is a three-month accounting or tax period. The change helps avoid confusion for English-speaking users and keeps financial terminology accurate.
Original PR description
A trimester is not a quarter. In the context of accounting and taxation, I doubt we mean a trimester here. This is Belgianese. Regards, the en_US police.
Task: https://www.odoo.com/web#active_id=2204990&cids=2&id=2204990&model=project.task&menu_id= Forward-Port-Of: odoo/enterprise#9407 Forward-Port-Of: odoo/enterprise#9386
Original PR description
Task: https://www.odoo.com/web#active_id=2204990&cids=2&id=2204990&model=project.task&menu_id= Forward-Port-Of: odoo/enterprise#9407 Forward-Port-Of: odoo/enterprise#9386
On any runbot instance, timesheet grid view: start a timer in the project "Research & Development" (the one with a timesheet not linked to any task). The "Unknown" timesheet is moving around and the name is set to the task of the started timer (the timer might be duplicated). taskID: 2160680 Forward-Port-Of: odoo/enterprise#7547
Original PR description
On any runbot instance, timesheet grid view: start a timer in the project "Research & Development" (the one with a timesheet not linked to any task). The "Unknown" timesheet is moving around and the name is set to the task of the started timer (the timer might be duplicated). taskID: 2160680 Forward-Port-Of: odoo/enterprise#7547
If there are manual INPUTS added after a payslip has been generated, there's no way to compute the payslip to view the resulting Salary Computation. This is done by recomputing the payslip. Otherwhise, on each added input this would require to trigger compute_sheet() automatically. Forward-Port-Of: odoo/enterprise#9169
Original PR description
If there are manual INPUTS added after a payslip has been generated, there's no way to compute the payslip to view the resulting Salary Computation. This is done by recomputing the payslip. Otherwhise, on each added input this would require to trigger compute_sheet() automatically. Forward-Port-Of: odoo/enterprise#9169
Deprecate MPD integration for Six payment terminals and replace it with TIM because: - MPD broadcasts connection messages to the network so having multiple terminals and MPD servers in the same network results in connection issues - TIM has a JS SDK so it doesn't require an IoT Box. - MPD supports only Yomani and Yoximo terminals while TIM also supports Ingenico. TaskID: 2188566 Forward-Port-Of: odoo/enterprise#8972 Forward-Port-Of: odoo/enterprise#8813
Original PR description
Deprecate MPD integration for Six payment terminals and replace it with TIM because: - MPD broadcasts connection messages to the network so having multiple terminals and MPD servers in the same network results in connection issues - TIM has a JS SDK so it doesn't require an IoT Box. - MPD supports only Yomani and Yoximo terminals while TIM also supports Ingenico. TaskID: 2188566 Forward-Port-Of: odoo/enterprise#8972 Forward-Port-Of: odoo/enterprise#8813