The stock forecast report now uses the proper currency when showing inventory values. This helps businesses avoid confusing or misleading financial figures in stock planning reports, especially when multiple currencies are involved.

Adds a test related to the fix 67d975be75963678d25ae54289b2f1de639c8bed

**Current behavior before PR:** A method action_subtask is including the other actions context if have which reflects while clicking on the Sub-tasks stat button. For examples: - When click on the stat button 'Sub-tasks' of any task which one is clicked by systray activity icon results - When click on the task menu in project there a default search filter 'My task' which also passes when click on 'sub tasks' stat button **Desired behavior after PR is merged:** Remove the cont

**Current behavior before PR:**

A method action_subtask is including the other actions context if have which
reflects while clicking on the Sub-tasks stat button. For examples:

- When click on the stat button 'Sub-tasks' of any task which one is clicked by
  systray activity icon results
- When click on the task menu in project there a default search filter 'My task'
  which also passes when click on 'sub tasks' stat button

**Desired behavior after PR is merged:**

Remove the context that startswith `search_default'.
Hence, now subtask will display with the correct context.

**LINKS:**
PR #65395
Task-2413127

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#65395

With this change, we show the variant price when printing ZPL product.product report and not the template as we did before. This way it is the same as what we see in Odoo as well as when printing PDF label of the product. targetting only 14.0 for now (but could be backported in stock_zebra) opw-2455291 Forward-Port-Of: odoo/odoo#66385

With this change, we show the variant price when printing ZPL
product.product report and not the template as we did before.

This way it is the same as what we see in Odoo as well as when printing
PDF label of the product.

targetting only 14.0 for now (but could be backported in stock_zebra)

opw-2455291

Forward-Port-Of: odoo/odoo#66385

Enter keypress browser event were removed in 3c372d1da8b. It was reintroduced in text fields with d2f024d2543 and in source mode of html field with b10ca1f6094b. When doing ENTER in the editor, we do our special case of ENTER (eg. it will split the container in two and have other custom behavior) but when doing SHIFT+ENTER we let the browser handle it and add a normal newline. With the "Enter" prevention, SHIFT+ENTER did not work. opw-2463746 Forward-Port-Of: odoo/odoo#66426

Enter keypress browser event were removed in 3c372d1da8b.

It was reintroduced in text fields with d2f024d2543 and in source mode
of html field with b10ca1f6094b.

When doing ENTER in the editor, we do our special case of ENTER (eg. it
will split the container in two and have other custom behavior) but when
doing SHIFT+ENTER we let the browser handle it and add a normal newline.

With the "Enter" prevention, SHIFT+ENTER did not work.

opw-2463746

Forward-Port-Of: odoo/odoo#66426

Before this fix, the extra button was out of the right edge of the screen. On desktop, m2o external buttons have to overflow over the right padding of the parent element. This is done to avoid to reduce the size of the input when the button appears (when a value is set). But on mobile, there is not enough padding and we therefore prefer to reduce the size of the field if an extra button should appear. To fix this, we simply ignore these rules on mobile. Note that the css selector t

Before this fix, the extra button was out of the right edge of the
screen.

On desktop, m2o external buttons have to overflow over the right padding
of the parent element. This is done to avoid to reduce the size of the
input when the button appears (when a value is set).

But on mobile, there is not enough padding and we therefore prefer to
reduce the size of the field if an extra button should appear.

To fix this, we simply ignore these rules on mobile.
Note that the css selector that really cause this issue was the one
related to '.o_row' and the second one has no effect.

Steps to reproduce:
- Go to "Inventory / Operations / Scrap"
- Click on "Create"
- Choose a product and set UOM field

Related task-ID: 1929043

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#66438

This commit ba32244c10396ff8605e5533e08675a64fbf9d88 introduced an error when validating pickings or reconciling Forward-Port-Of: odoo/odoo#66331

This commit ba32244c10396ff8605e5533e08675a64fbf9d88 introduced an error when
validating pickings or reconciling

Forward-Port-Of: odoo/odoo#66331

Issue - Init an instances of Odoo v13.0 'A' and v14.0 'B'. - Install "Accounting" app on instance A & B. - Set your email server on instance A & B. - Activate 'External email server' in settings of instance A. - Set an email alias for "Vendor Bills" on instance A. - Send a "Customer Invoice" from instance B to alias of instance A. - Fetch for new mail (in case new vendor bill don't appear) on instance A. - Open the new Vendor bill on instance A. Data are not parsed from pdf

Issue

	- Init an instances of Odoo v13.0 'A' and v14.0 'B'.
	- Install "Accounting" app on instance A & B.
	- Set your email server on instance A & B.
	- Activate 'External email server' in settings of instance A.
	- Set an email alias for "Vendor Bills" on instance A.
	- Send a "Customer Invoice" from instance B to alias of instance A.
	- Fetch for new mail (in case new vendor bill don't appear) on instance A.
	- Open the new Vendor bill on instance A.

	Data are not parsed from pdf attachment.

Cause

	No managing all attachements types:
	- list(tuple(str,str), tuple(str,str, dict) or int) attachments : list of attachment tuples in the form
          ``(name,content)`` or ``(name,content, info)``, where content is NOT base64 encoded
	- list id attachment_ids: list of existing attachement to link to this message
          - Should only be setted by chatter
          - Attachement object attached to mail.compose.message(0) will be attached
            to the related document.

Solution

	1. Remove overide of `message_post` since not used anymore
	2. Add/Overide `_message_post_process_attachments` to parse/create
	   any type of attachment and create related invoice.

	Since `_message_post_process_attachments` is already called in
	`message_post` of mail_thread.py in mail app, no need to process
	again attachments..

opw-2411002

Forward-Port-Of: odoo/odoo#64286
Forward-Port-Of: odoo/odoo#64165

Issue - Install "Sales" module - Go to settings and activate "Product Configurator" feature - Create a product X with mutilple color (variants) - Create a quotation - Add product X (Product Configurator should open) - Hover any color Popup with color name does not appear. Cause 'title' attribute value is removed. Solution Don't remove 'title' attribute value. opw-2438704 Forward-Port-Of: odoo/odoo#66451 Forward-Port-Of: odoo/odoo#65169

Issue

	- Install "Sales" module
	- Go to settings and activate "Product Configurator" feature
	- Create a product X with mutilple color (variants)
	- Create a quotation
	- Add product X (Product Configurator should open)
	- Hover any color

	Popup with color name does not appear.

Cause

	'title' attribute value is removed.

Solution

	Don't remove 'title' attribute value.

opw-2438704

Forward-Port-Of: odoo/odoo#66451
Forward-Port-Of: odoo/odoo#65169

*: google_recaptcha, website_form Issue - Install 'Ecommerce' module - In settings, fill the "reCAPTCHA: Easy on Humans, Hard on Bots" option with random wrong site key and secret key - Open your ecommerce (go to /shop ) - Add any product to cart and and open cart - Activate "Customize -> Extra Step Option" - Process to "Extra Info" step - Click on next Stuck at this step since next button does not react.

*: google_recaptcha, website_form

Issue

        - Install 'Ecommerce' module
        - In settings, fill the "reCAPTCHA: Easy on Humans, Hard
          on Bots" option with random wrong site key and secret key
        - Open your ecommerce (go to /shop )
        - Add any product to cart and and open cart
        - Activate "Customize -> Extra Step Option"
        - Process to "Extra Info" step
        - Click on next

        Stuck at this step since next button does not react.

Cause

        There is an error due to re-captcha feature that
        does not allowed to go to next step.

        The second issue is that the error is not displayed
        because missing message area in form.

Solution

        Do not check recaptcha if 's_website_form_no_recaptcha' class
        present in form.
        Add span 's_website_form_result' to display error messages.
        Replace 'public' by 'site' in error message to fit google
        'field' name.

opw-2456098

Forward-Port-Of: odoo/odoo#66382

In some situations, like during tests on runbot, the data-dir location may vary. With this commit, the `data-dir` CLI argument is added to the test_module_operations script. Forward-Port-Of: odoo/odoo#66422

In some situations, like during tests on runbot, the data-dir location
may vary.

With this commit, the `data-dir` CLI argument is added to the
test_module_operations script.

Forward-Port-Of: odoo/odoo#66422

Before this commit, the 'mounted' method of the ControlPanel in the traceability report was called twice. It happened because the traceability report updated the ControlPanel before being actually mounted, so mounted was called once when the traceability report was mounted, and once when the update was applied. Ideally, this should not be an issue (this isn't an issue with owl). However, in Odoo, we mix layers of Owl Components and legacy widgets. In these situations, the above scenar

Before this commit, the 'mounted' method of the ControlPanel in
the traceability report was called twice.

It happened because the traceability report updated the ControlPanel
before being actually mounted, so mounted was called once when the
traceability report was mounted, and once when the update was applied.

Ideally, this should not be an issue (this isn't an issue with owl).
However, in Odoo, we mix layers of Owl Components and legacy
widgets. In these situations, the above scenario isn't properly
handled (and can't be).

As a consequence, in mobile (enterprise), it crashed because an
handler bound in mounted (thus twice) was only unbound once.

This commit avoids the issue as the update was actually useless.

Steps to reproduces:
* Go to Manufacturing (MRP)
* Open the "burger menu"
* Select "Products" -> "Lots/Serial Numbers"
* Select one product in the list (unfold group first)
* Click on the "Traceability" ("stat button")
* Select one line to go to the form view
* Go back to the previous view using breadcrumb
* Optional: Go to another app if the screen can't scroll (e.g. go to Sales)
* Scroll the view => Bug

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#65522

When opening a document to sign (to edit it, not actually sign it) the sign box fields contains text that are not really readable due to their funky sizing (too big and truncated). This commit fixes it by making the font size relative to the one of the sign box and making it scale correctly. Also, it better aligns the move-handler and the responsible field. opw-2459952 Forward-Port-Of: odoo/enterprise#16477

When opening a document to sign (to edit it, not actually sign it) the
sign box fields contains text that are not really readable due to their
funky sizing (too big and truncated).

This commit fixes it by making the font size relative to the one of the
sign box and making it scale correctly. Also, it better aligns the
move-handler and the responsible field.

opw-2459952

Forward-Port-Of: odoo/enterprise#16477

Before this commit, the 'mounted' method of the ControlPanel in the account_reports was called twice. It happened because the account_reports updated the ControlPanel before being actually mounted, so mounted was called once when the account_reports was mounted, and once when the update was applied. Ideally, this should not be an issue (this isn't an issue with owl). However, in Odoo, we mix layers of Owl Components and legacy widgets. In these situations, the above scenario isn't pro

Before this commit, the 'mounted' method of the ControlPanel in
the account_reports was called twice.

It happened because the account_reports updated the ControlPanel before
being actually mounted, so mounted was called once when the
account_reports was mounted, and once when the update was applied.

Ideally, this should not be an issue (this isn't an issue with owl).
However, in Odoo, we mix layers of Owl Components and legacy
widgets. In these situations, the above scenario isn't properly
handled (and can't be).

As a consequence, in mobile (enterprise), it crashed because an
handler bound in mounted (thus twice) was only unbound once.

This commit avoids the issue as the update was actually useless.

Steps to reproduces:
* Go to Accounting
* Go to "Balance in GL" (Bank card)
* Unfold the 101402 Bank line
* Open the dropdown of one sub line (e.g. BNK1/2021/01/0001)
* Select view in the dropdown
* Go back to the previous view using breadcrumb
* Optional: Go to another app if the screen can't scroll (e.g. go to Sales)
* Scroll the view => Bug

Forward-Port-Of: odoo/enterprise#16033

Steps to reproduce the bug: - Let's consider two bank journals J1,J2 with SEPA CT activated - Let's consider two posted vendor payment using SEPA CT P1 for J1, P2 for J2 - Go to the accounting dashboard and click on Payment to send via SEPA of J1 Bug: P1 and P2 were displayed instead of P1 opw:2421293 Forward-Port-Of: odoo/enterprise#16480

Steps to reproduce the bug:

- Let's consider two bank journals J1,J2 with SEPA CT activated
- Let's consider two posted vendor payment using SEPA CT P1 for J1, P2 for J2
- Go to the accounting dashboard and click on Payment to send via SEPA of J1

Bug:

P1 and P2 were displayed instead of P1

opw:2421293

Forward-Port-Of: odoo/enterprise#16480

Issue - Install 'Helpdesk' module - Go to "Helpdesk" and edit "Customer Care" team - Enable "Website Form" feature, save and refresh - Go to website (with stat button) - Edit page and click on 'Attachment(s)' field - On right side menu, hover 'Label Position" options Traceback raised. Cause Field "Attachement(s)" not considered as custom. Solution Add 's_website_form_custom' class to 'Attachement' field to be considered as custom. opw-2446811 Forward-Port-Of

Issue

	- Install 'Helpdesk' module
	- Go to "Helpdesk" and edit "Customer Care" team
	- Enable "Website Form" feature, save and refresh
	- Go to website (with stat button)
	- Edit page and click on 'Attachment(s)' field
	- On right side menu, hover 'Label Position" options

	Traceback raised.

Cause

	Field "Attachement(s)" not considered as custom.

Solution

	Add 's_website_form_custom' class to 'Attachement' field
	to be considered as custom.

opw-2446811

Forward-Port-Of: odoo/enterprise#16466

Issue - Install `Subscriptions` module - Create a new subscription with: * Start Date = 02/09/21 * Date of Next Invoice = 03/01/21 * Add product `Office Cleaning Subscription (Monthly)` - Click on `Upsell` and set `Start Date` to 02/09/21 + add same product as above - Create and view quotation - Confirm and Create Invoice In production description, the start date is set to 02/08/21. Cause `Start Date` is altered so it can be used to calculate pro-rata upselling

Issue

	- Install `Subscriptions` module
	- Create a new subscription with:
	  * Start Date = 02/09/21
	  * Date of Next Invoice = 03/01/21
	  * Add product `Office Cleaning Subscription (Monthly)`
	- Click on `Upsell` and set `Start Date` to 02/09/21 + add same product as above
	- Create and view quotation
	- Confirm and Create Invoice

	In production description, the start date is set to 02/08/21.

Cause

	`Start Date` is altered so it can be used to calculate pro-rata upselling.

Solution

	Do not remove one day on `Start Date` that is displayed.

opw-2430090

Forward-Port-Of: odoo/enterprise#16236

Purpose ======= Allow all the employees to sign a new contract at the same time, while freezing all the inputs/selects, except the allowed ones on the link. Forward-Port-Of: odoo/enterprise#16450

Purpose
=======

Allow all the employees to sign a new contract at the same time, while
freezing all the inputs/selects, except the allowed ones on the link.

Forward-Port-Of: odoo/enterprise#16450

[FIX] account_reports: EC sales list: make the report 'strict_range' Before this fix, the selected range of dates wasn't strictly applied; so some lines from previous periods could be taken into account inc ase their account was of a type including initial balance. This is not what we want. v14 did properly, this behavior was introduced by the 14.1 refactoring of this report. [FIX] account_reports: EC sales list: don't consider UK as a member of EC after the Brexit [FIX] l10n_be_rep

[FIX] account_reports: EC sales list: make the report 'strict_range'

Before this fix, the selected range of dates wasn't strictly applied; so some lines from previous periods could be taken into account inc ase their account was of a type including initial balance. This is not what we want. v14 did properly, this behavior was introduced by the 14.1 refactoring of this report.


[FIX] account_reports: EC sales list: don't consider UK as a member of EC after the Brexit


[FIX] l10n_be_reports: add missing checks in Belgian's EC sales list implementation

Those were defined in the parent function, but super() is not called in Belgian version of the report.

Forward-Port-Of: odoo/enterprise#16456

Steps to reproduce: - Create a quality check with Type=Worksheet and Operations = Manufacturing - Create a Manufacturing Order and click on Quality Check button Expected behavior: shows worksheet form Actual behavior: shows a form with "Additional Note" field + "Fill in Worksheet" button. Pushing button then shows worksheet form. This commit makes it so worksheet form is immediately show. This change makes the behavior match what occurs when a worksheet quality check is triggere

Steps to reproduce:
- Create a quality check with Type=Worksheet and Operations =
  Manufacturing
- Create a Manufacturing Order and click on Quality Check button

Expected behavior: shows worksheet form
Actual behavior: shows a form with "Additional Note" field + "Fill in
  Worksheet" button. Pushing button then shows worksheet form.

This commit makes it so worksheet form is immediately show. This change
makes the behavior match what occurs when a worksheet quality check is
triggered in a picking.

Task: 2429092
X-original-commit: 34982fdb9050ca3c4d48cef6f983444f171253c6

Forward-Port-Of: odoo/enterprise#16467

Forward-Port-Of: odoo/enterprise#16414

Forward-Port-Of: odoo/enterprise#16414

When a multi_company check of all invoices is done, the compute fields crash as they uses self instead of record. In this case, self contains multiple companies and will make cron crash. Forward-Port-Of: odoo/enterprise#16436

When a multi_company check of all invoices is done, the compute fields crash as they uses self instead of record.
In this case, self contains multiple companies and will make cron crash.

Forward-Port-Of: odoo/enterprise#16436

Currently, When user move the ticket the close(solved) stage the close Date of the ticket will be added in close_date field. But when user move the ticket from closing stage to other stage at that time close date is not updated. So in this commint, When change the stage of tickets from the closing stage to other stage update the Close date to False. TaskID: 2379017 Forward-Port-Of: odoo/enterprise#16413 Forward-Port-Of: odoo/enterprise#16351

Currently, When user move the ticket the close(solved) stage
the close Date of the ticket will be added in close_date field.
But when user move the ticket from closing stage to other stage
at that time close date is not updated.

So in this commint, When change the stage of tickets from the closing
stage to other stage update the Close date to False.

TaskID: 2379017

Forward-Port-Of: odoo/enterprise#16413
Forward-Port-Of: odoo/enterprise#16351

When importing a CAMT bank statement, if the latter uses several currencies, the module may convert amounts unnecessarily. To reproduce the error, import this bank statement: [2439413_CAMT_example.xml](https://drive.google.com/file/d/1W4kAoZ4RQkrp1GjrLMSbwP_4BrQIpL-w/view?usp=sharing) Once done, the user is redirected to the reconciliation page and has to reconcile $1000. However, here is an extract of the CAMT bank statement XML: ```xml <Ntry> <Amt Ccy="USD">500.00</Amt

When importing a CAMT bank statement, if the latter uses several
currencies, the module may convert amounts unnecessarily.

To reproduce the error, import this bank statement:
[2439413_CAMT_example.xml](https://drive.google.com/file/d/1W4kAoZ4RQkrp1GjrLMSbwP_4BrQIpL-w/view?usp=sharing)
Once done, the user is redirected to the reconciliation page and has to
reconcile $1000. However, here is an extract of the CAMT bank statement
XML:
```xml
      <Ntry>
        <Amt Ccy="USD">500.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <AmtDtls>
          <TxAmt>
              <Amt Ccy="EUR">250</Amt>
              <CcyXchg>
                  <SrcCcy>EUR</SrcCcy>
                  <TrgtCcy>USD</TrgtCcy>
                  <XchgRate>2</XchgRate>
              </CcyXchg>
          </TxAmt>
        </AmtDtls>
	...
      </Ntry>
```
The original amount was 250€. Thanks to the change rate (2), the final
amount is $500. Therefore, the user should reconcile $500, not $1000.

For now, here is how the module calculates the amount of an entry:
```python
_get_amount = partial(_generic_get,
    xpath='ns:Amt/text() | ns:AmtDtls/ns:TxAmt/ns:Amt/text()')

_get_rate = partial(_generic_get,
    xpath='ns:XchgRate/text() | ns:AmtDtls/ns:TxAmt/ns:CcyXchg/ns:XchgRate/text()')

def _get_signed_amount(*nodes, namespaces):
    amount = float(_get_amount(*nodes, namespaces=namespaces))
    rate = float(_get_rate(*nodes, namespaces=namespaces)) or 1.0
    sign = _get_credit_debit_indicator(*nodes, namespaces=namespaces)
    return amount * rate if sign == 'CRDT' else -amount * rate
```
(From account_bank_statement_import_camt/wizard/account_bank_statement_import_camt.py)

`_get_signed_amount` and the XPaths need to be updated. In the above
case, `amount` is defined thanks to the first `<Amt>` node ($500).
However, `rate` is also defined (2). As a result, the module applies the
conversion again (this is the reason why the user has to reconcile $1000
instead of $500).

This fix first tries to use the data inside `<AmtDtls>` node ("Amount
Details"). If there isn't any amount, it uses the data directly present in
`Ntry` node. It then applies the conversion only if the amount currency
is different from the currency of the target conversion (`<TrgtCcy>`).

OPW-2439413

Forward-Port-Of: odoo/enterprise#16408
Forward-Port-Of: odoo/enterprise#16087

If a user, who doesn't have admins rights, tries to do an **Update Credentials**, he receives an error telling him that he doesn't have the right to access the _refresh_token_ variable. To solve this problem, the instruction _sudo()_ is added. Forward-Port-Of: odoo/enterprise#16428

If a user, who doesn't have admins rights, tries to do an **Update Credentials**, he receives an error telling him that he doesn't have the right to access the _refresh_token_ variable. To solve this problem, the instruction _sudo()_ is added.

Forward-Port-Of: odoo/enterprise#16428