Wednesday, February 3, 2021
8 changes · master
Enhancements to existing features
The contact form layout now keeps sales-related information together by moving the delivery carrier field away from the salesperson and sales team fields. This makes the form easier to scan and helps users find related sales details more quickly.
Original PR description
This commit keeps the sales related fields together in a contact form view by moving 'property_delivery_carrier_id' field out of in between 'user_id' (Sales Person) and 'team_id' (Sales Team). Task Id : 2445997
Email, phone, and website fields now only respond when users click the actual text, not the empty space beside it. This prevents accidental actions like opening an email client or dialing prompt while preserving long-text display behavior.
Original PR description
As the clickable area issue is also found in URL widget same as email widget we solved the issue by wrapping the anchor tag within a container div tag. Here, the overflow class will be on the container div which will do it's job to prevent the long strings from breaking the UI, and the anchor tag being its child, will not be the full width, thus limiting the clickable area. And in this commit some qunit test cases for phone widget is also changed as it is extended from email widget. task-id: 2345974
The system version number has been updated to mark the next alpha release in the master branch. This helps teams and stakeholders clearly identify builds, plan testing, and track progress toward the upcoming release.
The HR appraisal application has been renamed from "Appraisal" to "Appraisals" across the app switcher, menus, and settings. This provides clearer, more consistent wording for users throughout the interface.
Original PR description
PURPOSE Rename the app "Appraisal" into "Appraisals" Everywhere! App Switcher: https://drive.google.com/file/d/1zkZ3C1dE8-yvCUs1ochEcyJ_gL57ImIm/view?usp=drivesdk Appraisals App: https://drive.google.com/file/d/1eBaQOM4a7AIRSJCyL5OlLksIHWECi7Gr/view?usp=drivesdk Appraisals settings: https://drive.google.com/file/d/1P87sBTYN5-BhHVPU7j_CmBulRV5pehtZ/view?usp=drivesdk App => https://drive.google.com/file/d/1YkGI_NQ_NW-TcPIxzeL4V_fF3wHS5wfd/view?usp=drivesdk SPECIFICATIONS all given changes are updated. LINKS PR https://github.com/odoo/enterprise/pull/15422 Task-2414131
The VoIP module’s automated tests were updated to match recent changes that reduce the clickable area for phone, email, and URL fields. This helps ensure the calling interface behaves consistently and avoids accidental clicks in everyday use.
Original PR description
in this commit some test cases for phone-widget in voip is changed. task-id: 2345974
The contact form layout for Mexican electronic invoicing has been adjusted so sales-related information appears together. This makes the form easier to scan and helps users find related sales settings in one place.
Original PR description
This commit keeps the sales related fields together in a contact for view by moving 'l10n_mx_edi_external_trade' field at last, instead of after 'user_id' (Sales Person). Task Id : 2445997
This update adds and refreshes automated checks that protect key Helpdesk, Timesheet, Sales, and Field Service billing flows. It helps ensure the right sales order items are used, prevents invalid timesheet links, and keeps multi-company and billable project behavior reliable.
Original PR description
Purpose ====== The main goal of this PR is to write and update some unit tests about the changes made in Task-2388500, Task-2409761 and Task-2424382 to keep the functional features. ## Helpdesk App…
Purpose ====== The main goal of this PR is to write and update some unit tests about the changes made in Task-2388500, Task-2409761 and Task-2424382 to keep the functional features. ## Helpdesk App ### Determined Sales Order Items in ticket and timesheets When we create a ticket and set a customer who has a Sales Order with product services Sales Order Items ( = Sales Order Lines (SOLs)) then the SOL in the ticket is the one of latest SOLs if it is prepaid service and remaining_hours > 0. Otherwise, the SOL is False. For the timesheets in the ticket, the SOL on these ones are computed as the tasks when the pricing type in the project is equal to "Task Rate". That is, the SOL of each timesheet is the one set on the ticket. ### A timesheet cannot be linked to a task and a ticket A timesheet cannot be linked to a task and a ticket at the same time. Thus, we create a unit test to check if it is the case. ### Miscellaneous - Restore a step in helpdesk tour. ## Field Services App 2 tests have been created to check: - if the 'timesheet_product_required_if_billable_and_timesheets_and_fsm_projects' sql_constraint is raised when we try to erase the timesheet_product_id in billable fsm project. - if the pricing type of fsm project is only defined as "Task Rate". ## Miscellaneous Update the multicompany test, because this test used the project.task.sale.order wizard, this wizard has been removed (because it is unused). task-2439304 Related PR in Community: odoo/odoo#65146
Cohort view exports now use more descriptive file names that include the cohort context and the related model name. This makes downloaded files easier for users to identify, organize, and share without opening them first.
Original PR description
The purpose of this task is to clean up and provide clear export
file names.
Before this commit, When exporting data:
- from a cohort view, the file is named '<model description>Cohort'
After this commit, Name of the different export files as follows:
- for cohort view quick export, the file is named as
'Cohort of <model description> (<model technical name>)'
Task-Id: 2237840
PR: #15579