Fix 4c66eae3 attempted to translate terms but did not import _
This commit does just this

Purpose
=======

If you create an opp from the kanban you can select any contact (even if not marked "customer")

If you try to add a "non-customer" for the same field from the form view you cannot.

Specification
=============

Apply the same behavior than on the form view.

Uninstalling Sales with CRM still installed lead to an error
when clicking on CRM app because the dashboard_graph_model was not
updated for each crm.team record.

opw:748099

Some reports require additional information to render. When
accessed in Odoo, the user has to fill a wizard to provide those
information. However, when these reports were opened in Studio,
it crashed as those information were missing (we don't pass
through the configuration wizard in this case).

This fix checks if all the required information are given before
trying to render those reports, and it displays a warning in
the logs in they are missing, which is better than a traceback.

opw-748880

May be confusing for new users

Closes #17817

This fix 2e18070a66595a72a9a626a196c97a689832f667  has been done in stable and some customers
wants to keep the button "Post Inventory" available all the time.
Now the button is just visible in developper mode.

opw:748347

- Create a stockable product, get 61 units in stock
- Create a SO of 75 units, validate
- In the picking, transfer only 50 units, validate and create a
  backorder
- Print the Delivery Slip of the picking: it shows 61 units ordered
- Print the Delivery Slip of the backorder: it shows 61 units ordered
- Receive the 14 missing units, recheck availability on the backorder:
  it shows 25 units ordered

The quantity ordered should be recomputed from the stock moves when a
partial transfer is done.

opw-747983

- Update view with external_id=stock.view_move_picking_tree and remove
  editable attribute on the tree view.
- Create a new picking
- Add a line (form view will open) and click on "Save and close"

=> A traceback show up since 'scrapped' was not in the form view.

- The picking location fields become readonly, and the status bar
  disappears
- Save the picking

=> Error: "creation/update: a mandatory field is not correctly set :
   [object with reference: location_id - location.id]"

Courtesy of @benwillig

Closes #17738
opw-748353

Done at #17817

Steps to reproduce:

1. Create a new Stockable Product
2. Set cost price to 2.00
3. Adjust stock to 10 pcs
4. Enable developer mode
5. Go to Inventory > Reports > Inventory at Date
6. Select current time and retrieve the inventory value

Bug:

The stock valuation for the product was 0.0.

Reason:

When creating a stockable product, Odoo creates
two price history entries with the same datetime
but different cost. The stock valuation report only
takes one of them into account.

Fixes #14889

opw:747857

This is not how you check that a dict contains keys.

This also break the contract of method `get_html` that may now return
`None`, which `get_pdf` does not handle.

This reverts commit 0d2fb541.

Some were skipped due to API limit

The callback_eval field has a groups parameter of
base.group_system. Without this patch everyone not part of that group
ends up with an access right error when the system attempts to read
that field.

Previously this was not a problem because all code reading
callback_eval was executed with the superuser already. New code has
been introduced however that does not do this (eg. paying with a
payment.token from the backend).

opw-741181

Based on analysis https://gitlab.com/snippets/1665976

Closes #17815 

Was done poncutally but no global one since the release

This change will prevent the document from going from Done to Draft

In some cases a user may make that error functionally. It is only to have an additional validation

In the past, we didn't need this validations because the workflow didn't allow the use of a transition that is not defined on the correct state but since that we don't have workflow so we need manage this inconsistent action from original method in order to avoid a wrong transition.

Use full account names
The parent accounts have been removed but the account names have not changed.

Closes #17770

With the flow:
- create a contact with email address set
- click on smart button "opportunities"

When creating opportunity with the plain "create button", the opportunity gets its email_from correctly
whereas
when creating an opportunity from a kanban state's quick create, only the partner is set, and not the email_from

This commit aims at setting the email_from using either way of creating an opportunity

OPW 743698

Closes #17664

Some user might be logged but not have the right to access issue or task.
Plus it does not make any sense to redirect to backend after rating a task or an issue.

OPW: 748579

It calls `onchange_state()` on `res.partner` which was removed on
(24aba601).

It was added to `res.users` long ago (009ea409) to support a `state_id`
field on the view `res.users.simplified.form` that is no longer there
since v8.0.

The method is then never called and was crashing if called.

Closes #17772

If two MOs are using the same PO, when we cancel the first MO, the
check availability of second MO is not working.

The incoming shipment of the Purchase Order has the first MO's move_id
as the destination move. When we cancel the first MO, the incoming
shipment of Purchase Order still holds the first MO's move. Because of
that reason, the check availability is not working for the second MO.

While setting the destination move for the stock moves of the incoming
shipment, it should ignore the cancelled procurements.

Closes #17701
opw-748074

Courtesy of @suganthikarunanithi

If a user tries to reconcile already reconciled lines, the calling
method might have already filtered out these lines, and the method is
called with an empty self.

opw-748223

In case you have multiple warehouses and/or multiple manufacturing
locations (procurement routes), the same sequence is taken for the
created manufacturing order no matter where it is finally produced.

Closes #17681
opw-748344

Done at #17767

In case two reports have the same name (e.g. duplicate).
Accessing search only on the name which may not be unique.

Fixes #17751

Closes #16973

Steps to reproduce:

1) Go to Settings -> Technical -> User Interface -> Views
2) Create a new view and give only name, leave fields View Type and arch_base empty.
3) Exception occures

Current behaviour:
- The user gets an exception with a full stacktrace.
Expected behaviour:
- The user should get a warning