Closes #19910

And the SO item is readonly for sub task, to avoid
invoice twice the timesheet of a sub task.

The attachment should be create and linked to
the expense directly, and not on the expense
report (where it is readonly).

Create the sheet before opening a cached one avoid to
get error when computing computed field.

You do not have to specify it for themes

Closes #18039

IAP allow app publishers to charge for ongoing services. In that context, Odoo
acts mostly as a payment platform between the service user (client) and the service
provider (Odoo App developer).

Right column has been removed to have a clean checkout

- leftover real division errors
- typos in migration of values() calls in
  fffaf735

When the quickreate fail and a slow create is used instead, don't
display the error that happened as is done in kanban and calendar
(following 0f7f3fc2) quick create.

Commit f4200f37 aimed at avoiding 414 errors on too long uri.
But it brought up something else: on a new pos.config, the customer display html was not set due to that commit meddeling with the iframe's url.

This present commit forces the set up of the html field on create and write (according to the values, as usual)
the price to pay is to not being able to edit the html right away

Allow to order from several columns in inline tree views (x2many fields
in form views).

Support now that the read can receive id from calendar.event that
doesn't exists. And just ignore the inexisting ids.

Read(['start', 'start_datetime', 'start_date']) make the cache corrupt
for computed field start_datetime or start_date.

Now we don't read (for nothing ?) these 2 fields.

We can remove the skip for the test #500fabf1

Before this commit, a simple :
x = self.create({'name':'subject', 'allday': False, 'start': foo, 'stop': bar})

create randomly an event withtout start_datetime

Windows can be slower to start than that, sometimes.

Do not log a misleading "bad query" for cases where pg_database is not
accessible.

[FIX] website_sale_delivery: remove ES6 template literals in untested commit da3c561d

ES6 template literals are not supported in our testsuite / phantomjs
yet, which is why none of this branch's commit had passing tests >:-(

See #19841

Better English

Closes #19867

- value move lines created when the move is done
- when reducing done out move, increase latest in move in order to not
  lose the returned quantity in the fifo chain

In case you have a delivery partner set on your shipping contact,
when checkouting your cart, the preferred carrier will be used instead
of the first available carrier.

...commenting it while we find the bug.
Branch need to be green for v11

Before this commit, the priority of the view make that the warning was dipslayed between wishlist and comparator icon

The production_id on the stock move line is a helper field for work
orders and you can not assume it is always set correctly.  As
non-tracked stock moves create the stock move lines themselves it is not
set.

So, for logging notes, we check the 2 production order fields through
the moves.

Add a constraint in order to forbid it.

[FIX] account: onchange amount_currency in case of negative sign should set the credit (with a positive sign)

Before this fix, you can break a test class by simply adding an
incorrect import like this:
`from gloubiboulga import Casimir`
--> No error message, the test is simply not run

This is due to the fact that we want to ignore ImportError's... only
when there is no `.tests` submodules (actually, we ignored them all!)

This commit fixes the condition and re-enables error logging when tests
actually encounter ImportErrors

Initially, the check was done in _compute_practical_amount.
However, in case of no account_ids, an error is raised at each click until the account_ids are set.

was PR #19860 

test_03_test_serial_number_defaults creates 3 stock.production.lot
but in a test case they have the same create_date.
Moreover this test go through _assign_default_final_lot_id that do
a search on lot ordered by create date. That's why the test is non-
determinisitc since it could pick one of the 3 lots randomly

This commit add the id in the order.

When producing a finished product with a lot, also the raw materials
without lot tracking should split the move lines to at least know the
quantities consumed for every lot produced.  This way, the traceability
report will not confuse the user.

Typo error

_compute_package_info iterate on package but
sometimes self is used resulting in an ensure one
exception.

Since website refactoring, the behavior was lost and broke some snippets.

opw-768886