During reconciliation wizard, the wizard tries to find the best match with
exisiting unreconciled lines.
When more than one line could be reconciled with the bank statement line, the
oldest line was not selected.
e.g.
- statemement line: 10€
- invoice 1: 10€
- invoice 2: 10€
- invoice 3: 5€

The statement line was reconciled with the 5€ invoice instead of the first one.
This was due to the domain not matching when the exact same amount was found.

Sign CLA for compassionCH

Closes #8767

Avoid "patching" the registry, as this introduces inconsistencies (some field
attributes are lost).  Instead, proceed as follows:
 - update the definition of custom fields in database;
 - clear the corresponding cache on the registry (this was missing);
 - setup the models in registry (this reloads the custom models and fields);
 - update the database schema of the models based on the registry.

This makes the update of custom fields simpler and more robust.

closes #8783

To show the website_sale.modal, the product_variant_ids must be in the DOM
because all the prices are computed with the product_variant_ids.
From commit 0ff26cf7

opw:650167

Signed through OPW 650573

The domain for the analytic account in the `reconcile with writeoff` wizard
should be based on the `type` field, which must be `view`,
not on the `parent_id` field, as it's done everywhere else
(e.g. in the supplier invoice form).

`[('parent_id', '!=', False)]`
and
`[('type', '!=', 'view')]`
is almost the same, but the second domain is more appropriate.

Closes #4562

When creating the invoice of a sales order, from the sales order
(`Create invoice` button on the sale order),
the journal used for the invoice was forced
with a specific domain. Besides, the only reason the journal
is forced is to check there is a sale journal for the
quotation company, and raise a warning if not.
This check was added in 1578c285.

This prevented to use the user defined defaults,
(`Set defaults` in the `debug` menu)
to set a different default journal per user.

Using the `default_get` instead solves this issue,
as it uses first the user defined defaults. Besides,
if no user defined defaults are set, it then uses
the default value set in the field definition, which
in this case returns the same journal then the forced
domain mentioned above, the domain used being the same.

There is therefore no change of behavior, while giving
the possibility to use the user defined defaults.

Fixes #8786

Closes #8398

References to `date_end`
were previously corrected to `date_stop`,
in revision 98bd6732,
but one of them was missed.

Closes #4463

Closes #8460

In Sale Report Analysis, the price total must be in the currency
of the company.
Introduced by b5c1cb42
opw:649781

This revision adds the possibility to use the key
`default_category_id` in the context to set
the UoM category when quick creating a new UoM,
like it's the case everywhere else with the
`default_*` keys passed in the context.

Closes #4407

Test if the user gets notified for incoming contact requests.

Users subscribed to creation of records (new leads in a sales team, new
tasks in a project, etc.) are never notified. The reason is that users
were subscribed after the record creation notification.

Introduced in 43915a87
Closes #8723

To allow to translate "Wire transfer" in the ecommerce.

opw-650450

When ordering on the ecommerce,
if a payment transaction was found in the session,
this transaction was used as transaction for the current order.

Nevertheless, if the transction is no longer linked to
the current order, we should not use it.

This happened, for example, when the quotation
was deleted while the customer/user didn't close
its browser, and the transaction id was therefore
still in its session.

opw-650417

- Many CLA PRs initially fail the CLA check because the email
used in the signature is not the git committer email, so we
cannot match them.
- Minor spellchecking

This revision is related to:
 - 503820ac
 - 3b02e3d6

The taxes used to define the price must be the product taxes
of the company of the order.

Closes #8759

In a SO, the unit price of the suggested products must be computed with
the pricelist linked to this SO. Inspired from function 'product_id_change'
in model 'sale.order.line'.

opw:650168

For report with duplicated named headers, several columns could get
squashed together.

This fix check if a value is a duplicate or not, and if it is a
duplicates postfix an number allowing to differentiate the two headers
(for the human and the javascript).

This is the exact same solution than #6722
Backport of 5cff8fbb
opw-650000

The fetched ID was the one of the parent instead of the ID of the imported menu.

YAML import was missing support for loading values into fields
where `field.type == 'reference'`.

Use the original xml_id, which is present in the file, instead of the
checked one.

This change avoid to display the tasks
that a user is not permitted to see
in the reporting view 'Task analysis'

Closes #4399

Courtesy of jkei
https://github.com/jkei

use ustr() instead of str() to avoid traceback with translations

Closes #4272

This revision is related 420e198a.

onchanges can return "False" as warning value.
In such a case, prevent the concatenation with previous results.

Show lot_id on production wizard
if product is fully tracked
(but not marked specifically for production tracking

Closes #4223

If multiple warnings were returned by a cascading onchange
call, only the last warning was displayed.

This revision concatenates the warnings in such a case.

opw-649275

Reported by @yelizariev

closes #8737

This is possible that changes happen
during the loop in the multiple pickings:
an update in a picking could update another
picking. The browse must therefore be done
inside the loop to update the pickings with
the latest changes.

Fixes #4201

`ir.config_parameter` is readable by employees only.
It could happen to print a webkit report
as a portal / public user.

Closes #4181

In the module `purchase_double_validation`,
you can change the limit to require a second approval
in the purchase settings.

If the module was updated, the limit was re-set to
its default value.

Closes #4183

When adding a `%` in the followup letter content,
the constraint checking there is no syntax error
is supposed to raise a warning, telling '%' must
be set as `%%` when you want to display this percentage
char.

This constraint did not take into account the translation,
so when being in another language (e.g. French),
and adding a `%`, the warning was not raised, while
it should have been.

Closes #8680

Set security group as not updatable. To be able to not use fancy note

Closes #4178