Daily updates from Odoo
Thursday, March 4, 2021
5 changes · master
Enhancements to existing features
CRM reporting screens now provide clearer helper guidance for the Dashboard and Pipeline Analysis views, making it easier for users to understand and act on sales insights. Sample data was also removed from some lead generation reporting views so users see a cleaner, more relevant experience.
Original PR description
in this commit some reporting usability improvements are done in crm, the action helper for the dashboard and pipeline analysis are updated now and the sample data of cohort and dashboard views of lead generation are removed. task-id: 2393253
This update makes several marketing-related workflows easier to understand, especially in Social Marketing. Users get clearer guidance during the social setup tour and better feedback when newly created social streams have no posts yet, while activity forms are aligned with updated workflow options.
Original PR description
# Purpose General Marketing usability improvements based on what has been seen observing users on Fullstory. As the changes are relatively minor and related to specific apps, the rationale and improvements will be explained in more details in each commit. # Commits ##### [IMP] `social`: improve the social tour * change the position of a bubble * remove redundant steps ##### [IMP] `social`: display a toaster for new streams with no post in the feed * Add a feedback (toaster) for the user if no data can be fetch yet after a stream creation ##### [IMP] `mail`: revamp the activity type form view * See the Community commit with the same name (Enterprise update for the new fields) # Links Task ID : 2410217 COM PR : https://github.com/odoo/odoo/pull/63370 UPGRADE PR: https://github.com/odoo/upgrade/pull/2167
Resolved issues and error corrections
This fixes an issue where timesheet time units could ignore the company selected by the user in multi-company setups. Timesheet screens now load the correct company settings, helping ensure time entries are displayed and handled consistently across companies.
Original PR description
# Purpose This PR's primary objective is to ensure that the timesheet uom is working in accordance with the company settings in a multi company environment. Prior to this PR: - The timesheet related widgets initialisation process (adding the correct ones in the fieldRegistry) was performed before the front end treatment of cids and coockies which prevented applying the front end selected company settings. After this PR: - Timesheet widgets are initialised during the AbstractWebClient init and are in sync with the multicompany front end settings task-2168337 Related PR: odoo/odoo#66551
This fixes an issue where products added and then removed from a field service task could still appear as delivered on the related delivery order. When a task is marked done, the system now flags delivery orders that need manual review instead of validating incorrect quantities automatically.
Original PR description
Before this commit, when we create SO with FSM product and Inventory product. After that, when we add one product to the FSM task then we remove that product. So even if the product quantity is zero, it displayed in the delivery order linked to the SO that 1 quantity has been delivered when the quantity delivered is zero. In this commit, when the FSM user marks the task mark as done, then the system will generate the exception activity for the delivery order. Task-Id:2370887 PR: #16065
Code cleanup and technical improvements
The field service product quantity control was redesigned so users can adjust quantities directly with integrated plus and minus buttons or manual entry. The update also improves usability by preventing flickering, resizing the quantity display for larger numbers, and adding tests to protect the behavior.
Original PR description
Purpose ====== In `industry_fsm_sale` module, the fsmProductQuantity widget is creating and manipulating dom elements which is not a best practice design. In addition, the '+' and '-' buttons are not part of it, these buttons are part of the kanban view. That's why a refactoring of this widget is made. ## Details - Review the template xml of this widget - Add the both buttons in this widget. - Use the method defined in the FieldInteger widget to keep the functional behaviour when the user manually edits the quantity. - Apply some changes to improve the usability of this widget. ### Additionnal points - When the user clicked on the quantity span, the display name of the product was flicker. This visual problem has been fixed. - When the user manually edits the product quantity, the span tag automatically resizes based on the number of digits. - Add unit tests in JS to validate the widget. task-2447258