Before this commit, the allocated percentage calculation of shifts planned on many days was wrong because it uses the old allocated percentage as a ratio to compute the new one. This commit updates the calculation to avoid using the old allocated percentage to compute the new one to correctly compute based on working schedule of the resource/company and the allocated hours set on those shifts. Forward-Port-Of: odoo/enterprise#34568

Before this commit, the allocated percentage calculation of shifts planned on many days was wrong because it uses the old allocated percentage as a ratio to compute the new one.

This commit updates the calculation to avoid using the old allocated percentage to compute the new one to correctly compute based on working schedule of the resource/company and the allocated hours set on those shifts.

Forward-Port-Of: odoo/enterprise#34568

In some tests, we create standard views to test that we take the original arch of a view to create an inline one. Before this commit, a typo `<t t-groups="" />` instead of `<t groups="" />` slipped through the review process. After this commit, those typos are corrected. Forward-Port-Of: odoo/enterprise#34561

In some tests, we create standard views to test that we take the original arch of a view to create an inline one.

Before this commit, a typo `<t t-groups="" />` instead of `<t groups="" />` slipped through the review process.

After this commit, those typos are corrected.

Forward-Port-Of: odoo/enterprise#34561

# Current behaviour Due to a recent modification (#32299), field-services that should be invoiced based on timesheet, were invoiced based on the ordered quantity. # Expected behaviour Invoicing a service with an invoice policy of delivered timesheet, should be invoiced as such, not based on orderd quantity. # Steps to reproduce - Install Field Server, Sales, Inventory - Create a SO with "Field Service" as product, set the quantity to 4 - Confirm the SO - Go to the generated task and

# Current behaviour
Due to a recent modification (#32299), field-services that should be invoiced based on timesheet, were invoiced based on the ordered quantity.

# Expected behaviour
Invoicing a service with an invoice policy of delivered timesheet, should be invoiced as such, not based on orderd quantity.

# Steps to reproduce
- Install Field Server, Sales, Inventory
- Create a SO with "Field Service" as product, set the quantity to 4
- Confirm the SO
- Go to the generated task and log 1:30 hours in the timesheet.
- Validate the service
- Generate the invoice
- Observe the invoiced quantity is not the correct (4 instead of 1:30)

# Reason for the problem
The referenced change was setting manually qty_delivered, regardless of the type of the invoicing of the field service.

# Fix
Add additional condition to not set the qty_delivered on the sol, when that service has a service_policy of "Delivered Timesheet".

# Affected versions
- 14.0
- 15.0
- saas-15.2
- saas-15.3
- 16.0
- master

opw-3074219

Forward-Port-Of: odoo/enterprise#34557
Forward-Port-Of: odoo/enterprise#34456

Steps to reproduce: - Enable both "Create new barcodes" and "using existing barcodes" on an operation type. - Configure a product with a barcode and tracked via lots or serial number - Scan the product from the operation type with both "Create new barcodes" and "using existing barcodes" enabled - Scan a new lot barcode that hasn't already been created What is the current behavior? - If you click edit, the lot/serial number isn't listed What is the expected behavior? - The lot/ serial

Steps to reproduce:
- Enable both "Create new barcodes" and "using existing barcodes" on an operation type.
- Configure a product with a barcode and tracked via lots or serial number
- Scan the product from the operation type with both "Create new barcodes" and "using existing barcodes" enabled
- Scan a new lot barcode that hasn't already been created

What is the current behavior?
- If you click edit, the lot/serial number isn't listed

What is the expected behavior?
- The lot/ serial number should be populated in the edit screen when both "Create new barcodes" and "using existing barcodes" are enabled.

Solution:
When scanning a product with the 2 options (add to existing lot and create a new lot) enabled on the receipt configuration,
 there are two conditions that clash to choose which of the fields lot_name (field for new lot) or lot_id (field for an existing lot) will be shown.
It seems that it's the first one which wins and that's why even if we scan a product for an existing lot, the lot_id is retrieved but the
empty lot_name is shown. Just fix those conditions to look after each other.

opw-2925763

Forward-Port-Of: odoo/enterprise#34118
Forward-Port-Of: odoo/enterprise#30363

Multiple words can be set as selected if there are duplicates in the OCR results. This caused a traceback during the validation as it is expected that only one word is marked as selected. Forward-Port-Of: odoo/enterprise#34511

Multiple words can be set as selected if there are duplicates in the OCR results.
This caused a traceback during the validation as it is expected that only one word is marked as selected.

Forward-Port-Of: odoo/enterprise#34511

In this commit, we have added the NOT segment and set the EMI_8 tag value in the Vendor bills XML. TaskID - 3044039 Forward-Port-Of: odoo/enterprise#34500 Forward-Port-Of: odoo/enterprise#33691

In this commit, we have added the NOT segment and set the EMI_8 tag value in the
Vendor bills XML.

TaskID - 3044039

Forward-Port-Of: odoo/enterprise#34500
Forward-Port-Of: odoo/enterprise#33691

wrong date Have a LU company setup Go to Accounting>Reporting>Profit&Loss Set manually date range 01/01/2022 - 31/12/2022 Click "Export ECDF Declaration" and export XML In the generated XML CA_BILAN section will have date range 1/12/2022 - 31/12/2022 opw-2956155 Forward-Port-Of: odoo/enterprise#31803 Forward-Port-Of: odoo/enterprise#31439

wrong date

Have a LU company setup
Go to Accounting>Reporting>Profit&Loss
Set manually date range 01/01/2022 - 31/12/2022
Click "Export ECDF Declaration" and export XML

In the generated XML CA_BILAN section will have date range 1/12/2022 - 31/12/2022

opw-2956155

Forward-Port-Of: odoo/enterprise#31803
Forward-Port-Of: odoo/enterprise#31439

The tooling has been introduce in later version of odoo. It is a problem when somebody switches to older branches without disabling the tooling as it would then try to commit the tooling config files. We just add a few lines in the gitignore to prevent this issue. Forward-Port-Of: odoo/enterprise#34526 Forward-Port-Of: odoo/enterprise#34518

The tooling has been introduce in later version of odoo. It is a problem when somebody switches to older branches without disabling the tooling as it would then try to commit the tooling config files.

We just add a few lines in the gitignore to prevent this issue.

Forward-Port-Of: odoo/enterprise#34526
Forward-Port-Of: odoo/enterprise#34518

Steps to recreate the issue: - Log in as Mitchell - Create a new company, let's call it c2 - c2 should now be an allowed company of Mitchell, but not their preferred one. - go to Settings > Manage Companies, drag c2 to the top of the list - Go to Calendar > Online appointments - Activate 'create opportunity' - Via Website, create a new appointment as public user (log off Mitchell), complete form (name, email, phone) and confirm appointment - Sign back in as Mitchell - Go to calendar

Steps to recreate the issue:

- Log in as Mitchell
- Create a new company, let's call it c2
- c2 should now be an allowed company of Mitchell, but not their
preferred one.
- go to Settings > Manage Companies, drag c2 to the top of the list
- Go to Calendar > Online appointments
- Activate 'create opportunity'
- Via Website, create a new appointment as public user (log off
Mitchell), complete form (name, email, phone) and confirm appointment
- Sign back in as Mitchell
- Go to calendar: appointment is created with new contact (assignee)

Issue:

In CRM, the generated lead does not appear in Mitchell's preferred
company, but in c2. This happens because the lead's company_id
is chosen as env.company, which is set to the company with the
lowest sequence. Overall, this can confusing to the employee. 

This commit adds the employee company as extra context to the lead creation.

opw-2951087

Forward-Port-Of: odoo/enterprise#34520
Forward-Port-Of: odoo/enterprise#30497

Fix workorder times problems: - sum in workorders list view (displays numeric value rather than mins:secs) - timers sometimes starts at -00:01 - almost all tablet view actions reset the timer (click burger, ...) - clicking pause stops the timer at the next second - seconds are lost in employee timers - fix employee list display in workorder form view task: 2985735 Forward-Port-Of: odoo/enterprise#33796

Fix workorder times problems:
- sum in workorders list view (displays numeric value rather than mins:secs)
- timers sometimes starts at -00:01
- almost all tablet view actions reset the timer (click burger, ...)
- clicking pause stops the timer at the next second
- seconds are lost in employee timers
- fix employee list display in workorder form view

task: 2985735

Forward-Port-Of: odoo/enterprise#33796

We no longer display when a consent expire date is too far away from the current date. It only shows when it's going to expire 7 days before or less. task-3043449 Forward-Port-Of: odoo/enterprise#33340

We no longer display when a consent expire date is too far away from the current date. It only shows when it's going to expire 7 days before or less.

task-3043449

Forward-Port-Of: odoo/enterprise#33340

- Fixes issue when working on a bom with variants, where it would always pick the first the first variant for the parent bom when looking at a component instead of picking the right variant. - Fixes bom overview not loading when PLM is installed but the user opening the report has no rights in the PLM app. Part of task-2985735 Related to odoo/odoo#104893 Forward-Port-Of: odoo/enterprise#33613

- Fixes issue when working on a bom with variants, where it would always pick the first the first variant for the parent bom when looking at a component instead of picking the right variant.
- Fixes bom overview not loading when PLM is installed but the user opening the report has no rights in the PLM app.

Part of task-2985735

Related to odoo/odoo#104893

Forward-Port-Of: odoo/enterprise#33613

When a user makes a payment following the link from the "Generate Payment Link" wizard and the amount differs from the expected amount of the order we should not create an invoice automatically -as this will update the "next invoice date" without the customer having fully paid for that period. opw-3083809 Forward-Port-Of: odoo/enterprise#34509 Forward-Port-Of: odoo/enterprise#34461

When a user makes a payment following the link from the "Generate Payment Link" wizard and the amount differs from the expected amount of the order we should not create an invoice automatically -as this will update the "next invoice date" without the customer having fully paid for that period.

opw-3083809

Forward-Port-Of: odoo/enterprise#34509
Forward-Port-Of: odoo/enterprise#34461