The propagation of procurement group is not applied when a procurement
generates a PO.

opw-659331

The Kanban view has been refactored recently, and the communication mechanism
between the view and its cards changed. The cards now communicate with the
view by triggering_up custom events.

The code in dashboard overrides the function open_record of the Kanban view to
allowing opening a record by clicking on a card directly from the dashboard.
Unfortunately, this code hasn't been adapted after the Kanban refactoring.

There was a weird bug on chrome when there was a scrollbar in the sidebar, as
the right part of the client action overlapped that scrollbar. The problem was
seemingly linked to the use of flex, which is removed by this rev.

Courtesy of QSM

If an issue project is changed, depending if the destination project has
a set partner ("Customer") or not:

- if set, the project issue partner will be set accordingly
- otherway the potentially set partner will be conserved

Since 3fe06da6 if the project had not partner, the partner was unset
which is undesired.

Commit bb1200ad introduced the automatic
addition of cc as followers of tasks and issues. However it seems to
automatically create partners if the address it not recognized. This
does not seem a good idea.

[FIX] analytic: workaround to re-enable the feature to close an analytic account that has been unfortunately removed by mistake in commit 2a8c077f.

It is using an already existing field that wasn't used anymore ('account_type') but as a lot of domains on analytic accounts were
 - wrong (still using old fields state and type that have been removed as well in the same commit),
 - or defined directly in the views
so, an update of some modules may be needed in order to avoid further problems.

[FIX] account_voucher: company_id field of account.voucher has to be a related of the journal's company

[FIX] analytic: propagate the context of the related action when opening the analytic chart of account

They are hidden in mobile mode, but we don't want to deactivate chat
windows in website livechat.

- don't display user name in chat windows
- scroll to the new messages separator if it exists (in client action)
- increase sidebar width
- add correct link href in threads
- hide chat window in mobile mode
- mail: ignore o_mail_redirect or o_channel_redirect, but redirect anyway

The `binay_image` and `content_disposition` are moved
from the web controller to the `ir.http` model,
to be able to override these methods.

This makes possible to browse the records images as sudo
when the record is published on the website.
e.g. to see the partner images on the website `/partners` page
from the `website_crm_partner_assign` module.

opw-659244

Do not hardcode the version in the search but use the current version of the
server.

Closes #9987, opw 658811

when there is a view_id parameter in the url, the web client should
honor that request, instead of using default view

Allow for both sale and purchase taxes since using a sale tax on a writeoff
makes sense in cash basis accounting.

Trim message as in Discuss and do not send empty messages

If the user clicks twice on the 'x', the chat window is closed

The condition was never verified as prod_obj.type is a field.
Closes #9931

Otherwise all emails are scheduled in the queue.

Put the whole adresse, to avoid having it prefixed by a domain.

We force to recompute the taxes on all lines when we change the fiscal position.
That was already done in backend, with the onchange.
But @api.contrains allow to do it on each write on fiscal_position_id field.

@api.Depends will not work because it is not a computed field.

m2m_tags in list editable view try to get color on validation, the field is invalid because the mutex is pending.
Fix: use internal_set_value (don't re-rendering)

Issue: steps to reproduce:
- Create a new instance, install "sale"
- Create a product "prepayment", service, invoice on ordered qties
- Create aproduct "project phase", service, invoice on delivered qties, manually track delivered qties
- Create a SO with once prepayment, and twice a line with "project phase". ( the name (description) of the lines should be "phase 1" and "phase 2" )
- Create invoice => The prepayment is invoiced
- Go back to the SO, try to change the delivered qties of the first phase to 1
- Save => error, odoo doesn't let you save.

Do not hide the menu entries when the column is empty, because the column is
not re-rendered after you quick-create records in it.

This allow to keep route with an SignedIntConverter with more
priority than a StringConverter.

The default wight is 100, so force the weight to 50 (default intConverter)
was also a fix. But we decide to rewrite the SignedIntConverter based on the
intConverter of WerkZeug.

So now, a controller '/module/<string:xmlid>', will be matched after
'/module/<int:id>". (Same behaviour that before the commit 800ae137)

Group discount related fields
Closes #9944

comment stating date of currency rates
As all rates where moved in demo data

Closes #10017

When receiving an email containing two attachments(.docx, .odt) with the chatter
the icons displayed for the two attachments were the icon of a zip file instead
of the icon of a document file.

ps: the dictionnary "mapping" with the mimetypes and the signatures has been
changed in a tuple of tuples to keep the order of the mimetypes because
all the document files (.docx, .dot) begin by 'PK\x03\x04' and all the
zip files by 'PK'.

opw:658706

opw-658973

Searching on res.partners with domain [('user_ids' , '!=', False)]
will currently be translated into a huge "ID IN <...>"  query,
with the IDs of all existing users.
On a database with a lot of users, this can be measured
in seconds (e.g. 3-4 seconds with 500k+ users),
leading to significant delays in email delivery.

Using a direct lookup in res.users is more direct and faster.

If a kanban tile is moved to another column, in case of failure it
would stay in that column giving the false idea that it somewhat worked.

This commit refresh the kanban view in such an instance.

closes #9837

first half of opw-657863

When editing an email template with the wysiwyg,
the `<` and `>` operators are automatically converted
to `&lt;` and `&gt;`, even for the Jinja2 conditions,
therefore breaking these conditions, and the render
of the email templates.

We avoid to use these operators in the email
template, so users can customize the notification
email template without having an advanced
knowledge on how to edit an email template containing
Jinja2 code.

Besides, the line return at the end of the email template,
just after the `% endif`,
is done on purpose as well: the wysiwyg adds automatically,
at the time of this revision,
`<p></p>` at the end of the email template source, but
this cannot be added on the same line than `% endif`,
otherwise this is considered as Jinja2 code, and it's not.

opw-659113

opw-657955

t-field expects a UTC datetime which it then localizes to the current
viewer's timezone (using context tz from the browser), but goal here was
to display the event's own local time, so t-field was provided an
already localized datetime and would parse it as UTC then re-offset it
based on the user's timezone, resulting in a completely nonsensical
displayed datetime.

Just display the localized datetime without reprocessing it (save to
slice off the seconds count)

[FIX] web_editor: enter in a p tag empty (when user change with code view) can be raise an exception