Monday, May 18, 2020
36 changes · master
Enhancements to existing features
This update streamlines accounting company onboarding steps and removes an unused Colombian localization field from contact records. The changes reduce maintenance complexity and help keep the user interface focused on relevant information.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The SMS form view has been cleaned up so it better matches the SMS composer experience. This makes reviewing SMS details and performing basic actions more consistent and easier for users.
Original PR description
Purpose ======= Clean up of the sms form view to match what is shown in the composer as well as allowing basic actions. Task-2244195
This update replaces remaining uses of the word “leave” with “time off” in HR-related warnings, labels, emails, and messages. It makes employee-facing wording clearer and more consistent across the Time Off and Presence areas without changing business processes.
Original PR description
Followup on a3daff6 Use `time off` word instead of 'leave'. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website filter labels have been renamed to make them easier for users to understand. This improves usability by helping website managers find and apply the right filters more quickly.
Original PR description
Usability Improvement Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now click anywhere inside a checkbox cell in list views to select or unselect a record, instead of needing to click precisely on the checkbox. This makes selecting multiple records faster and less frustrating.
Original PR description
**PURPOSE**: Currently, the hitbox(the clickable area which can check & uncheck the checkbox) for the checkbox in listview is limited upto the border of the checkbox. User have to specifically click within or on the border of the checkbox to change the status of the checkbox to checked & unchecked. It is quite cumbersome for the user to select multiple checkboxes quickly. So to improve user usability, the hitbox area of the checkbox is increased by making the cell clickable. So if user click outside the checkbox but within the cell will also change the status. **SPEC**: We have bind click event for the respected cell of that checkbox. and click on that will change the stauts of the checkbox of that particular cell. Task : 2247387
Kanban cards in CRM, Recruitment, Maintenance, and Project no longer show the unread message action counter. Users can still find records needing attention through existing notifications and filters, while day-to-day boards become simpler and less visually crowded.
Original PR description
PURPOSE After discussion, we concluded that we are better off removing the message_needaction_counter field from the kanbans for the following reasons: the user has access to unread messages on…
PURPOSE After discussion, we concluded that we are better off removing the message_needaction_counter field from the kanbans for the following reasons: the user has access to unread messages on records from the discuss item in the systray it is irrelevant for user handling notifications through their mail client it is only less UI item to worry about on the kanban views (as features increase, we need to be careful not to clutter the views) the user can still use the message_needaction filter to get records with unread messages SPECIFICATION Remove message_needaction_counter field from every kanban view https://drive.google.com/file/d/1IRT7ZQcIRKJ21Ggk5jpExTenaKzcMDM-/view?usp=sharing AFAIK the message_needaction_counter field is used in the following kanban views crm.crm_case_kanban_view_leads crm.view_crm_lead_kanban helpdesk.helpdesk_ticket_view_kanban hr_recruitment.hr_kanban_view_applicant maintenance.hr_equipment_request_view_kanban mrp_plm.mrp_eco_kanban project.view_task_kanban LINKS PR: #51299 TaskID: 2257624 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Kanban cards in Helpdesk and PLM no longer show the unread message counter, reducing visual clutter in day-to-day views. Users can still find unread messages through Discuss, email notifications, or existing unread-message filters.
Original PR description
PURPOSE After discussion, we concluded that we are better off removing the message_needaction_counter field from the kanbans for the following reasons: the user has access to unread messages on…
PURPOSE After discussion, we concluded that we are better off removing the message_needaction_counter field from the kanbans for the following reasons: the user has access to unread messages on records from the discuss item in the systray it is irrelevant for user handling notifications through their mail client it is only less UI item to worry about on the kanban views (as features increase, we need to be careful not to clutter the views) the user can still use the message_needaction filter to get records with unread messages SPECIFICATION Remove message_needaction_counter field from every kanban view https://drive.google.com/file/d/1IRT7ZQcIRKJ21Ggk5jpExTenaKzcMDM-/view?usp=sharing AFAIK the message_needaction_counter field is used in the following kanban views crm.crm_case_kanban_view_leads crm.view_crm_lead_kanban helpdesk.helpdesk_ticket_view_kanban hr_recruitment.hr_kanban_view_applicant maintenance.hr_equipment_request_view_kanban mrp_plm.mrp_eco_kanban project.view_task_kanban > check if there are others LINKS PR: #10613 TaskID: 2257624 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update changes a warning message in the Time Off app to use the term “time off” instead of “leave.” It keeps wording consistent and easier for employees and managers to understand.
Original PR description
Followup on a3daff6bc121a42bf293ca91b8f522c26bac7c8a Use `time off` word instead of 'leave'. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
The eLearning module now handles invitation-related field values through a single automatic calculation approach instead of separate default and change-time rules. This keeps behavior consistent while reducing maintenance complexity, with no intended change for end users.
Original PR description
… computed field PURPOSE Try to move from onchange / default_get to stored editable computed fields. Behavior should be the same (computed or set by user), with support of create / write / onchange field update without additional code. SPECIFICATIONS Update classic fields updated in some cases by onchange and/or default methods by fields with store=True, readonly=False. It means their value comes either from manual user input, either from trigger based computation. Remove onchange and default_get when possible, leading to an unique computation method and clearing fields definition. Also clean some fields definition inconsistencies, notably required fields that should instead be correctly computed or default that have no real meaning. LINKS Task ID : 2229048 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Forward-port of PR https://github.com/odoo/odoo/pull/49964 Forward-Port-Of: odoo/odoo#49968
Original PR description
Forward-port of PR https://github.com/odoo/odoo/pull/49964 Forward-Port-Of: odoo/odoo#49968
Fixes issues in the Website countdown snippet editor so users no longer see an extra blank area when dragging a custom countdown block. It also prevents an error when resetting the background color for countdown snippets using the box layout, making page editing more reliable.
Original PR description
in this commit: - remove extra blank canvas from section, while dragging a custom countdown snippet. - fix traceback error while reset a layout background color of box layout countdown snippet. task-2227149 Closes #50907 Co-authored-by: dwa-odoo <dwa@odoo.com> Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where older color settings were not properly cleared when users edited website snippets. It also makes matching legacy colors appear selected when they correspond to a current theme color, helping users see and manage existing designs more reliably.
Original PR description
Colorpalette compatibility system was broken so old color classes were not removed from snippets when being edited. The bug was introduced by [1]. Also if a compatibility color class happens to use the same css color as a current theme class, that one will now be shown as selected. [1]: https://github.com/odoo/odoo/commit/c20423313cf10f262e615badc0397e6ba4ef4087
Point of Sale sessions with a configured customer display no longer show an error when opened. This helps stores using customer-facing screens start checkout smoothly without disruption.
Original PR description
An error showed when opening a POS with a customer display configured.
The system now records when automatically generated export references are created. This helps administrators identify and clean up old entries in a potentially large internal table, improving long-term database maintenance.
Original PR description
This table could be huge and we need a way to identify old records in order to vacuum them
Task 2253452, issue initially reported by @Whenrow So far the SSF had a pretty ad-hoc handling of O2Ms (as far as extracting values for onchange & save calls goes anyway) and basically completely ignored nested o2ms as that's not exactly a frequent usage. MRP managed to need an o2m (tree, invisible) inside an o2m (tree, editable) inside a form *and* messing with it in various onchanges, so the time of bliss hath ended. Turns out this also requires that the nested o2m already has lines, as
Original PR description
Task 2253452, issue initially reported by @Whenrow So far the SSF had a pretty ad-hoc handling of O2Ms (as far as extracting values for onchange & save calls goes anyway) and basically completely…
Task 2253452, issue initially reported by @Whenrow So far the SSF had a pretty ad-hoc handling of O2Ms (as far as extracting values for onchange & save calls goes anyway) and basically completely ignored nested o2ms as that's not exactly a frequent usage. MRP managed to need an o2m (tree, invisible) inside an o2m (tree, editable) inside a form *and* messing with it in various onchanges, so the time of bliss hath ended. Turns out this also requires that the nested o2m already has lines, as "new" records are more or less untouched by the SSF and thus less likely to be in an odd state. Anyway the main issue is `onchange_values` would clean up the editable o2m e.g. send nothing for unmodified entries & only send values for modified fields otherwise, but the nested one would skip this step and would do things like send UPDATE commands with an `id`, which would blow up when loading the record in cache in the backend (in master anyway). Convert `_onchange_values` to work recursively, so that all o2ms with relevant contents are properly cleaned up. Also found a somewhat related issue on save, `UPDATE` commands of nested o2ms which had not been touched would not get hydrated to full records, and ultimately the SSF would try to write `None` on the records, which doesn't work. Convert these to `4` matching onchanges as a `4` should be a more efficient version of a no-op `1`, and might avoid issues with over-eager write overrides and the like. Forward-Port-Of: odoo/odoo#51315 Forward-Port-Of: odoo/odoo#51298
Bug === In the portal, the user can say that he's interested by a lead. He can write a comment, but this comment is not escaped. Task-2228921 Forward-Port-Of: odoo/odoo#50197 Forward-Port-Of: odoo/odoo#49521
Original PR description
Bug === In the portal, the user can say that he's interested by a lead. He can write a comment, but this comment is not escaped. Task-2228921 Forward-Port-Of: odoo/odoo#50197 Forward-Port-Of: odoo/odoo#49521
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51342
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51342
Bug === Go to CRM, in the lead list view and select a lead without phone number. Then, click on the action "Send SMS Text Message". Then, enter in debug mode and go to the SMS form view. The number will be "0" instead of being empty. Task-2244195 Forward-Port-Of: odoo/odoo#50203
Original PR description
Bug === Go to CRM, in the lead list view and select a lead without phone number. Then, click on the action "Send SMS Text Message". Then, enter in debug mode and go to the SMS form view. The number will be "0" instead of being empty. Task-2244195 Forward-Port-Of: odoo/odoo#50203
Issue - Install website - Go to Website->Configuration->Pages - Group By "View" - Open and edit "Home" view of "My Website 2" - Remove "Website" value and save - It should list 2 same views for same url and no website under one of the "Home" views - Go to Configuration->Settings - Create a new website Traceback is raised. Cause When fetching default homepage, it retrieve more then one pages and then try to assign it as homepage to new website. Solution
Original PR description
Issue - Install website - Go to Website->Configuration->Pages - Group By "View" - Open and edit "Home" view of "My Website 2" - Remove "Website" value and save - It should list 2 same views for same url and no website under one of the "Home" views - Go to Configuration->Settings - Create a new website Traceback is raised. Cause When fetching default homepage, it retrieve more then one pages and then try to assign it as homepage to new website. Solution Limit query to one to get only one homepage. opw-2252208 Forward-Port-Of: odoo/odoo#51216
Add Total Receivable and Total Payable to contacts list view. Create Vendor Bill for a partner with $0 Receivable and Payable - the Payable amount is updated in the list view. Create an invoice for this partner - the Total Payable is changed to $0, and the Total Receivable is updated in the list view. Create a Vendor Bill for a partner having a Receivable amount - the Payable is not updated. This occured after commit 9920f20e4c7753bc17bea71dea3a90f7de687196 In a situation in which the
Original PR description
Add Total Receivable and Total Payable to contacts list view. Create Vendor Bill for a partner with $0 Receivable and Payable - the Payable amount is updated in the list view. Create an invoice for this partner - the Total Payable is changed to $0, and the Total Receivable is updated in the list view. Create a Vendor Bill for a partner having a Receivable amount - the Payable is not updated. This occured after commit 9920f20e4c7753bc17bea71dea3a90f7de687196 In a situation in which the lines retrieved from the db are arranged like |pid| type | val | |---|-----------|-----| | 10| payable| 500| | 14| receivable| 200| | 14| payable| 300| line 3 will cancel line 2 because partner credit will be set to false after the debit update. Fixing by checking that the same partner has not been processed yet opw-2250989 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51228
When we build a new box we make a update && upgrade of the raspbian image. But it upgrade "firmware-brcm80211" from version "1:20190114+rpt4" to "1:20190114+rpt5" With this update and when Odoo run on the box the "wifi access point" can't be activated With this commit we unabled the update of this package and keep the "1:20190114+rpt5" Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed
Original PR description
When we build a new box we make a update && upgrade of the raspbian image. But it upgrade "firmware-brcm80211" from version "1:20190114+rpt4" to "1:20190114+rpt5" With this update and when Odoo run on the box the "wifi access point" can't be activated With this commit we unabled the update of this package and keep the "1:20190114+rpt5" Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#48684
- Employees > Configuration > Planning Types and ensure the activity type "To Do" is set to scheduled date several days after previous activity (default should be 5 days); - Check that onboarding Plan has at least 2 activities with activity type "To Do"; - Click launch plan. Before this commit, the activity type configuration is ignored and all activities are due tomorrow. Now, the activities are due taking into account the activity type configuration. opw-2255586 Fo
Original PR description
- Employees > Configuration > Planning Types and ensure the activity
type "To Do" is set to scheduled date several days after previous
activity (default should be 5 days);
- Check that onboarding Plan has at least 2 activities with activity
type "To Do";
- Click launch plan.
Before this commit, the activity type configuration is ignored and all
activities are due tomorrow.
Now, the activities are due taking into account the activity type
configuration.
opw-2255586
Forward-Port-Of: odoo/odoo#51381
Forward-Port-Of: odoo/odoo#51347- Activate routing - Go to Inventory > Deliveries > New Planned Transfer - Add a line => the 'Demand' field is editable - Save - Edit => the 'Demand' field is not editable anymore The field should be editable as long as the picking is draft. It seems working at creation because the fields `show_operations` and `is_locked` are not yet computed yet. It happens because `picking_id` is not in the tree view. We change the read-only condition: if `is_initial_demand_editable` is `
Original PR description
- Activate routing - Go to Inventory > Deliveries > New Planned Transfer - Add a line => the 'Demand' field is editable - Save - Edit => the 'Demand' field is not editable anymore The field should be editable as long as the picking is draft. It seems working at creation because the fields `show_operations` and `is_locked` are not yet computed yet. It happens because `picking_id` is not in the tree view. We change the read-only condition: if `is_initial_demand_editable` is `True`, the field is editable. opw-2257498 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51352
- Install Inventory, base_automation - Create an automated action on stock.quant, trigger on Update, code raise Warning('My Warning') - Create a transfer on a stockable product with e.g. 10 quantity on hand e.g. Initial demand is 9 ⁻ Mark as todo and Check Availability: on the transfer the reserved quantity is not updated, but on the stock.quant it is updated to 9. You can check availability again and nothing will happen on the transfer, the stock.quant "Reserved" will be updated each ti
Original PR description
- Install Inventory, base_automation
- Create an automated action on stock.quant, trigger on Update, code
raise Warning('My Warning')
- Create a transfer on a stockable product with e.g. 10 quantity on hand
e.g. Initial demand is 9
⁻ Mark as todo and Check Availability: on the transfer the reserved
quantity is not updated, but on the stock.quant it is updated to 9.
You can check availability again and nothing will happen on the
transfer, the stock.quant "Reserved" will be updated each time though.
You can update the quantity on hand to 0, and you will get
products with Reserved Quantity when Quantity in Hand is 0, and no
MO/Transfer or any other activity holding the reservation.
opw-2245109
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#51180Description of the issue/feature this PR addresses: Expected singleton error fired when installing an addon that adds more than 1 equipment demo data with preventive configuration. Current behavior before PR: When installing addons with some demo data (e.g. with serveral equipments with preventive maintenance configuration), the `_compute_next_maintenance` method is fired in order to compute the `next_action_date` field. But, if more than 1 equipment is called, an expected singleton error i
Original PR description
Description of the issue/feature this PR addresses: Expected singleton error fired when installing an addon that adds more than 1 equipment demo data with preventive configuration. Current behavior before PR: When installing addons with some demo data (e.g. with serveral equipments with preventive maintenance configuration), the `_compute_next_maintenance` method is fired in order to compute the `next_action_date` field. But, if more than 1 equipment is called, an expected singleton error is fired at `maintenance.py`:190 (call to self field instead of for current variable, called equipment in an `api.multi` method) Desired behavior after PR is merged: `self` wrong reference is changed, then the singleton error will not be fired any more. If this PR is merged, it should be cherry-picked in v13 al well. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#45438
Before this commit, the `Create Employee` button was not visible if user is linked to employee in any other company as the domain was based on `employee_count`. (Which represents Employee belongs to all companies) With this commit, we check for `employee_id` which makes sure if the user has linked Employee for currently activated company. Followup on 95564bcd2c7ee42f25e07b7319c28b22b41dc46f Description of the issue/feature this PR addresses: Current behavior before PR: Desired beh
Original PR description
Before this commit, the `Create Employee` button was not visible if user is linked to employee in any other company as the domain was based on `employee_count`. (Which represents Employee belongs to all companies) With this commit, we check for `employee_id` which makes sure if the user has linked Employee for currently activated company. Followup on 95564bcd2c7ee42f25e07b7319c28b22b41dc46f Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51356
- fix multicompany issue in payment links generated through the wizard - avoid polluting the url of invoice payment links with unnecessary kwargs when sale is installed - fix stripe issue with ideal fix Forward-Port-Of: odoo/odoo#51382
Original PR description
- fix multicompany issue in payment links generated through the wizard - avoid polluting the url of invoice payment links with unnecessary kwargs when sale is installed - fix stripe issue with ideal fix Forward-Port-Of: odoo/odoo#51382
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51418 Forward-Port-Of: odoo/odoo#51383
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51418 Forward-Port-Of: odoo/odoo#51383
### Issue - Install Contacts - Create a contact: Company A - Add a contact to that company: John - Add a private address for John - Save - Change John's company - Go back - Look for the private address The display_name contains the old company name ### Cause The private address display_name is not recomputed when the contact's company changes. ### Solution Recompute child_ids display_name when the company changes. **OPW-2253785** -- I confirm I
Original PR description
### Issue - Install Contacts - Create a contact: Company A - Add a contact to that company: John - Add a private address for John - Save - Change John's company - Go back - Look for the private address The display_name contains the old company name ### Cause The private address display_name is not recomputed when the contact's company changes. ### Solution Recompute child_ids display_name when the company changes. **OPW-2253785** -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#51335
Steps to reproduce the bug: - Go to inventory > settings > enable multiple warehouses - Let's consider the default warehouse W - Create a new warehouses NW - Enable debug mode - Go to sales > create a new quotation - Go to the other information tab > change default warehouse W to the newly created warehouse NW - Click on the bug > go to set defaults > warehouse=NW > save default - Refresh the page > Go to sales > create a new quotation - Go to other information tab > observe the wareh
Original PR description
Steps to reproduce the bug: - Go to inventory > settings > enable multiple warehouses - Let's consider the default warehouse W - Create a new warehouses NW - Enable debug mode - Go to sales > create a new quotation - Go to the other information tab > change default warehouse W to the newly created warehouse NW - Click on the bug > go to set defaults > warehouse=NW > save default - Refresh the page > Go to sales > create a new quotation - Go to other information tab > observe the warehouse Bug: The warehouse was W instead of NW opw:2254084 Forward-Port-Of: odoo/odoo#51177 Forward-Port-Of: odoo/odoo#51143
In fb051d3420 there was some changes on drag and drop of chatter windows, but this would break the drag and drop of summernote because it wait for document.drop event for hiding the drop zone. opw-2259522 Forward-Port-Of: odoo/odoo#51448
Original PR description
In fb051d3420 there was some changes on drag and drop of chatter windows, but this would break the drag and drop of summernote because it wait for document.drop event for hiding the drop zone. opw-2259522 Forward-Port-Of: odoo/odoo#51448
PURPOSE Fix trace state management in mass mailing: correctly compute state and better support incoming email headers. SPECIFICATIONS: STATE Trace status is a computed field based on other fields. Those store the datetime at which a specific action has been performed: opened, replied, bounced, ... depending on those fields status of trace is computed. Replied / Bounced / Opened states should be computed prior to Sent state. Indeed Sent is the default state once the email is sent.
Original PR description
PURPOSE Fix trace state management in mass mailing: correctly compute state and better support incoming email headers. SPECIFICATIONS: STATE Trace status is a computed field based on other fields.…
PURPOSE Fix trace state management in mass mailing: correctly compute state and better support incoming email headers. SPECIFICATIONS: STATE Trace status is a computed field based on other fields. Those store the datetime at which a specific action has been performed: opened, replied, bounced, ... depending on those fields status of trace is computed. Replied / Bounced / Opened states should be computed prior to Sent state. Indeed Sent is the default state once the email is sent. Then replied, bounced and opened are states that happen after sending the email. It is therefore necessary to re-order the state computation to correctly compute the statistic state. SPECIFICATIONS:GATEWAY Consider an email going through the mail gateway. Its headers References and In-Reply-To are used in mail gateway to find if it is an answer to an existing discussion thread. Notably in mass mailing it is used to set mailing traces (called statistics in 11.0) as opened and replied. However currently only the References header is used. In this commit we now use References or In-Reply-To like what is done in mail gateway. LINKS Task ID 2257717 PR #51247 Forward-Port-Of: odoo/odoo#51445 Forward-Port-Of: odoo/odoo#51247
The scheduling view has shown a performance bottleneck on database with high numbers of serial numbers. After analysis of the SQL view definition, a join in the subquery can be removed to simplify queries and improve performance. opw-2229482 Forward-Port-Of: odoo/enterprise#10638 Forward-Port-Of: odoo/enterprise#10545
Original PR description
The scheduling view has shown a performance bottleneck on database with high numbers of serial numbers. After analysis of the SQL view definition, a join in the subquery can be removed to simplify queries and improve performance. opw-2229482 Forward-Port-Of: odoo/enterprise#10638 Forward-Port-Of: odoo/enterprise#10545
The FSM/stock integration is broken with product tracked with serial numbers. Go to a new FSM task > Products > try to add a tracked product => nothing happens. A wizard to manage the serial number should open Task 2245645 Forward-Port-Of: odoo/enterprise#10212
Original PR description
The FSM/stock integration is broken with product tracked with serial numbers. Go to a new FSM task > Products > try to add a tracked product => nothing happens. A wizard to manage the serial number should open Task 2245645 Forward-Port-Of: odoo/enterprise#10212
Since 8c03446, to find the contact of an incoming call, a sanitized process is done to add the international code if is missing. This relay in the inviteSession.remoteIdentity.uri.type parameter, which is not always set. Now a fallback is done, it checks if the last 6 digits of the phone number corresponds to the last 6 digits of a phone number in the contact. Like this we can find the contact without having the international code. opw-2254068 Forward-Port-Of: odoo/enterprise#10620
Original PR description
Since 8c03446, to find the contact of an incoming call, a sanitized process is done to add the international code if is missing. This relay in the inviteSession.remoteIdentity.uri.type parameter, which is not always set. Now a fallback is done, it checks if the last 6 digits of the phone number corresponds to the last 6 digits of a phone number in the contact. Like this we can find the contact without having the international code. opw-2254068 Forward-Port-Of: odoo/enterprise#10620
The defaults hours of FSM are set to: - planned_date_begin=9:00 - planned_date_end=17:00 But they are set incompatibly with how calendar view create event and so when you create a new event from 2:00 to 3:00 in calendar view you will also get 9:00 to 17:00. opw-2254420 Forward-Port-Of: odoo/enterprise#10621
Original PR description
The defaults hours of FSM are set to: - planned_date_begin=9:00 - planned_date_end=17:00 But they are set incompatibly with how calendar view create event and so when you create a new event from 2:00 to 3:00 in calendar view you will also get 9:00 to 17:00. opw-2254420 Forward-Port-Of: odoo/enterprise#10621