Daily updates from Odoo
Navigate
Branch
Thursday, March 4, 2021
19 changes
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
A ready-to-use email template is now available for Field Service interventions. This helps teams communicate intervention details to customers more easily and reduces setup effort when configuring project stages.
Original PR description
Before, when we can't provide any details of the intervention. By this commit, we are facilitating configuration by providing a default email template to communicate the details of the intervention. task - 2417291 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
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
Helpdesk security rule labels were renamed to make their purpose easier to understand. This reduces confusion for administrators reviewing access and multi-company settings without changing how the rules work.
Original PR description
Rename all Project: multi-company to better interpretable name in the helpdesk module
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
Miscellaneous changes
Because of 4de8d37661da9344120e187c81efe5f22cae9b2d the invisible checkbox was broken i.e. the wrong data was taken to compute the invisible checkbox for a field Have a view arch: ``` <tree> <field name="fname" invisible="1" /> </tree> ``` Before this commit, when entering the view editor sidebar for that field, the invisible checkbow was not checked Clicking on it sent instructions, but at the return of edit_view, the checkbox was not computed correctly After this commit, ever
Original PR description
Because of 4de8d37661da9344120e187c81efe5f22cae9b2d the invisible checkbox was broken i.e. the wrong data was taken to compute the invisible checkbox for a field Have a view arch: ``` <tree> <field name="fname" invisible="1" /> </tree> ``` Before this commit, when entering the view editor sidebar for that field, the invisible checkbow was not checked Clicking on it sent instructions, but at the return of edit_view, the checkbox was not computed correctly After this commit, everything works as expected OPW 2466705 Forward-Port-Of: odoo/enterprise#16855 Forward-Port-Of: odoo/enterprise#16837
Rename all Project: multi-company to better interpretable name in the helpdeks module Forward-Port-Of: odoo/enterprise#16834
Original PR description
Rename all Project: multi-company to better interpretable name in the helpdeks module Forward-Port-Of: odoo/enterprise#16834
… tax The partner_id was always False when looking up for the tax records to use. This happened because the function was called before the partner_id was set on the record. Forward-Port-Of: odoo/enterprise#16827
Original PR description
… tax The partner_id was always False when looking up for the tax records to use. This happened because the function was called before the partner_id was set on the record. Forward-Port-Of: odoo/enterprise#16827
Having a default of qty_done = 1.0 for quality checks didn't make sense in any case when the qty to do wasn't 1.0. This made it so if a workorder was started before the work order's components are reserved then the qty_done would be stuck on 1.0 instead of the reserved quantity after the components are reserved. Steps to reproduce: - create a BOM with a component and a component quantity != 1 (make sure the component is in stock) - add an operation with a "Register Consumed Materials
Original PR description
Having a default of qty_done = 1.0 for quality checks didn't make sense in any case when the qty to do wasn't 1.0. This made it so if a workorder was started before the work order's components are reserved then the qty_done would be stuck on 1.0 instead of the reserved quantity after the components are reserved. Steps to reproduce: - create a BOM with a component and a component quantity != 1 (make sure the component is in stock) - add an operation with a "Register Consumed Materials" Step with "Product To Register" = the component - create a MO with the BOM => confirm => click on Tablet view of the generated WO - WO will display Quantity = 1.00 / 0.00 Units - Return to MO and click "Check Availability" => click on WO Tablet view again Expected result: Quantity = BOM quantity / 0.00 Actual result: Quantity = 1.00 / 0.00 opw-2448484 Forward-Port-Of: odoo/enterprise#16823
At first, when we click on view planning in employees it shows the traceback. However, that issue would be solve. Task ID: 2463614 Forward-Port-Of: odoo/enterprise#16740
Original PR description
At first, when we click on view planning in employees it shows the traceback. However, that issue would be solve. Task ID: 2463614 Forward-Port-Of: odoo/enterprise#16740
Before this commit, when the user creates a planning slot template with: - start_hour = 11 pm - duration = 3 hours and he wants to add a planning.slot using this template in the employee E's planning, the date range of this shift is on the same date and the end_datetime is less than start_datetime. Moreover, this problem implies negative allocated hours. This commit removes the difference done with the previous end date of the slot and the new computed end date to recalculate correc
Original PR description
Before this commit, when the user creates a planning slot template with: - start_hour = 11 pm - duration = 3 hours and he wants to add a planning.slot using this template in the employee E's…
Before this commit, when the user creates a planning slot template
with:
- start_hour = 11 pm
- duration = 3 hours
and he wants to add a planning.slot using this template in the
employee E's planning, the date range of this shift is on the
same date and the end_datetime is less than start_datetime.
Moreover, this problem implies negative allocated hours.
This commit removes the difference done with the previous end date of
the slot and the new computed end date to recalculate correctly this
date with only the template.
We can ignore the defined range of days previously defined because the
compute for the end_datetime (called `_compute_datetime`) in
planning.slot is not no longer triggered by a change in the data of the
employee linked to the planning.slot but only the template (done in
this commit: 4a7ce5cb7 ).
Cause of this bug:
- Commit: 87bd8a5
Impacted versions:
- 14.0 and above versions
Steps to reproduce:
1. Create planning.slot.template with these information:
- date_start: 11 pm
- duration: 3 hours
2. Go back to the gantt view of planning and click on the '+' button
when we hover a day in the gantt view.
3. Create this planning.slot using the template created before for a
employee E.
Current behaviour:
- The date range of this planning.slot is on the same day. For
instance, we have the start_datetime is equal to 1/1/2021 at 11pm
and the end_datetime is equal to 1/1/2021 at 2am.
Expected behaviour:
- The date range of this planning.slot should be on 2 days and not only
one to have positive allocated hours. If we retake our example above,
the start_datetime should be equal to 1/1/2021 at 11pm and the
end_datetime should be equal to 1/2/2021 at 2am. And then, the allocated
hours should be 3 hours (the duration in the template).
task-2463619
Forward-Port-Of: odoo/enterprise#16707Before this commit, clicking on the "</> xml" button triggered an error. This was because studio wanted to mount a component in a widget without using a compatibility adapter. opw-2464475 Forward-Port-Of: odoo/enterprise#16818 Forward-Port-Of: odoo/enterprise#16802
Original PR description
Before this commit, clicking on the "</> xml" button triggered an error. This was because studio wanted to mount a component in a widget without using a compatibility adapter. opw-2464475 Forward-Port-Of: odoo/enterprise#16818 Forward-Port-Of: odoo/enterprise#16802
Otherwise, the file gets refused by intervat. Forward-Port-Of: odoo/enterprise#16790
Original PR description
Otherwise, the file gets refused by intervat. Forward-Port-Of: odoo/enterprise#16790
Purpose ======= Mark the payment at today allows to process it as soon as possible (For example ING allows to set a date from 5 days before to 6 months). Currently when setting the processing date at payslip.date_from, if this the last day of the month a sunday, the paiment file is generated on Thuesday or Friday, and the payment is not processed until Monday during the night. Forward-Port-Of: odoo/enterprise#16737
Original PR description
Purpose ======= Mark the payment at today allows to process it as soon as possible (For example ING allows to set a date from 5 days before to 6 months). Currently when setting the processing date at payslip.date_from, if this the last day of the month a sunday, the paiment file is generated on Thuesday or Friday, and the payment is not processed until Monday during the night. Forward-Port-Of: odoo/enterprise#16737
Before this commit, when helpdesk dashboard grouped then it is not displayed below dashboard value div, it is displayed besides it so grouped kanban view is not displayed and screen has horizontal scroller, to view kanban view user have to scroll screen After this commit, helpdesk dashboard grouped kanban view will be displayed below dashboard value div TaskId: 2424177 Forward-Port-Of: odoo/enterprise#16779 Forward-Port-Of: odoo/enterprise#16020
Original PR description
Before this commit, when helpdesk dashboard grouped then it is not displayed below dashboard value div, it is displayed besides it so grouped kanban view is not displayed and screen has horizontal scroller, to view kanban view user have to scroll screen After this commit, helpdesk dashboard grouped kanban view will be displayed below dashboard value div TaskId: 2424177 Forward-Port-Of: odoo/enterprise#16779 Forward-Port-Of: odoo/enterprise#16020
Before this commit, the quote character was not escaped in the name in the pivot formula, which could lead to crash if the content contains a quote. Steps to reproduce: - Create pivot view on Products - Create a product with a quote in his name - Add field "Name" to the pivot view - Insert in spreadsheet => traceback opw-2453997 Forward-Port-Of: odoo/enterprise#16785 Forward-Port-Of: odoo/enterprise#16780
Original PR description
Before this commit, the quote character was not escaped in the name in the pivot formula, which could lead to crash if the content contains a quote. Steps to reproduce: - Create pivot view on Products - Create a product with a quote in his name - Add field "Name" to the pivot view - Insert in spreadsheet => traceback opw-2453997 Forward-Port-Of: odoo/enterprise#16785 Forward-Port-Of: odoo/enterprise#16780
Forward-Port-Of: odoo/enterprise#16795
Original PR description
Forward-Port-Of: odoo/enterprise#16795