Graph view legend items are shortened when ther are too long.
Here we add tooltips on hover to allow the user to see the
full text of items that were cut.

We also improve a bit the way items are shortened.

Co-Authored-By: Thomas Werland <twe@odoo.com>

Update of Chart.js library to the latest version.
The onLeave listener was not avalaible in the previous version of the library.
This has also removed a bug in the graph view where
some groups were sometimes not shown in the legend.

Co-Authored-By: Thomas Werland <twe@odoo.com>

Co-Authored-By: Thomas Werland <twe@odoo.com>

Share the logic for delivered and procurement quantities computation. In
some edge cases, the differences between them triggered an unexpected
behaviour such as showcased in the added tests.

closes odoo/odoo#35257

Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>


Co-authored-by: Arnold Moyaux <arm@odoo.com>

The commit https://github.com/odoo/odoo/commit/d3dc5048e40d1aef693336d10ce582d39ce17337 from v11 should be removed, as in v12 becomes dead code because the commit https://github.com/odoo/odoo/commit/93ae1b1a041b6a36521263ff87ac980e6102551a

 deleted the _get_exceptions_domain method.

closes odoo/odoo#35256

Signed-off-by: Simon Goffin (sig) <sig@openerp.com>

This module is not fully featured and also outdated so now we remove this module

closes odoo/odoo#35007

Signed-off-by: Josse Colpaert <jco@openerp.com>

test_putaway_6 creates 2 putaway rules on the same product category but to different location.
As the order on putaway rule is [sequence, product_id] and the two have the same sequence,
it can happens that the choosen rule is not always the same,

Furthermore, the test tried to show the hierarchy between two category matters in term
of putaway rule.

This commit create a child category of 'all' and set it on one of the rule.

closes odoo/odoo#35264

Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>

The `cash_control` constraint [1] is only relevant when the field
`cash_control` is modified. Do not check it when opening the pos UI.

[1] added by 733fb360

Oversight of previous forward-port.

when opening the sale promotion in mass mail, it creates a traceback
due to invoice compute method as it does not have invoice id because
of changes in account.move.

task-2036203

closes odoo/odoo#35202

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>

The onboarding modal for setting up the few base fields of a company
has now been moved to a wizard
It is accessible from the general settings, but also in the onboarding
section of sale and account modules.

The following company settings are editable with that wizard:

- Set report **layout**:
The user can chose the overall look of the report. The current choices
are : *Standard* (default), *Background*, *Boxed* and *Clean*.

- Set company **logo**:
Changes the company logo.

- Set report **colors**:
The user can set the primary and secondary colors of the report through
a newly added widget allowing to pick a custom color.
When changing the **logo**, colors are automatically set to its most dominant
colors.
> A "Reset colors" button also triggers the color calculation.

- Set report **font**:
Changes the overall font of the report. Only Google Fonts are used
for enhanced compatibility.

- Company **tagline**, also called "header"
- **Footer**
- **Paper format**
- Report **preview**:
A mockup of a final report
Automatically updates when changing **layout**, **logo**, **colors** or **font**

Co-authored by: Julien Mougenot <jum@odoo.com>

closes odoo/odoo#33863

Signed-off-by: VincentSchippefilt <VincentSchippefilt@users.noreply.github.com>


Co-authored-by: Lucas Perais <lpe@odoo.com>

Added a boolean option to toggle opacity settings on the colorpicker dialog widget.
When set to true, both the opacity slider and the opacity input are hidden in the
dialog. When not set or set to false, opacity settings remain unchanged.

The reason this widget was moved is that the next improvement
([IMP] base: Configure document layout) defines a new field (FieldColor)
which needs to call the colorpicker dialog inside of the base module.
This couldn't be done while the dialog was located in the wysiwyg assets.

The color field is necessary to be able to display some fields
(many2many_tags) and used in the kanban views

closes odoo/odoo#35216

Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

The commit f3999314 introduces a
declaration of non-existing `uninstall_hook` in the manifest, causing
error when trying to uninstall the sale_timesheet_purchase module.
This commit simply removes it.

Task #2039731

closes odoo/odoo#35106

Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>

Before this commit, the stock's setting Advanced Scheduling was always
visible, even when it's empty. Now, it is invisible until sale_stock or
purchase_stock makes it visible (it's needed because they each add an
option into it).

Task #2039731

Task #2039731

In the Inventory Valuation report, values must be grouped by product_id.

Task #2039731

In the picking form view, places the picking type field before location
fields, thus user is prompt to set it before locations because the
onchange on the picking type erases the location fields.

Task #2039731

How to reproduce:
- Active multilocation in inventory setting;
- Go on product form view;
- Click on Update Quantity / On Hand button;
- Create a new quant.

With stock_account, we encounter a traceback when creating a new quant
in some case where the `location_id` isn't set by default, because it
tries to compute the value and it checks location to know if the quant
must be valueted or not.

Task #2039731

On stock list view of a single product, when user click on "Inventory at
Date" button, the displayed report shows all products.
This commit makes the report only shows the current product.

Task #2039731

Before this commit, the field `lot_id` was hidden when useless for the
editable quant list, but was always present in the readonly quant list.
Now, the `lot_id` is hidden when appropriate in the two lists.

closes odoo/odoo#35008

Signed-off-by: Simon Lejeune (sle) <sle@openerp.com>

Some quant can have no company_id (quant for partner locations).
But when user edit a quant, the stock move `company_id` is based on the
quant's one. As the `company_id` is required for a stock move, we force
to take the `company_id` of the user in case the quant don't have one.

Task #2035465

As quant from inventory loss location balances real quantity, it could
be really hazardous to able user to modify it. That said, modify it now
has no effect. So, with this commit, we exit the quant write method in
case of user tries to modify it manually if the quant location is
inventory loss, and we inform the user he can't modify it.

We could set the field as readonly in this case, but it's clearer for
user to inform him/her in case he/she tries to modify the quant than set
the field as readonly and take the risk user don't understand why he/she
can modify some quant and can't modify some other.

It would be preferabler to raise an UserError in the write than do
nothing in the write and return a warning in the onchange, but in case
we raise an error in the write method, user side the field is still in
edit mode and then, every time user clicks somewhere but on Discard, it
will raise the error again and it's not convenient for the user.

Task #2035465

This commit moves some ir_ui_view specific functions into ir_ui_view.py
and removes some old-api <-> new-api compatibility shims as well as
removes orm.py since it has 0 to do with the Odoo ORM.

closes odoo/odoo#34826

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

Purpose
=======

Currently, when we click on “Settings” on the Home Dashboard, we arrive
on a new Dashboard with several pieces of information like Installed Apps,
invite new users, or translations. Some informations are reachable in
several ways, which is not necessary.

We would like to remove this page and replace it with the General Settings
page directly. That makes more sense to the user who click on “Settings”. The
present informations will be dispatched in the menu or in the general settings
for a better usability.

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

This commit move code from web_settings_dashboard in order to put the features
in settings directly. To do so, we choose to move code to base_setup, and create
widget on the settings form view to keep features. Concerned features are: invite
users, dev tools, odoo edition number and IAP account link.

TaskID: 2006910

closes odoo/odoo#34290

Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

closes odoo/odoo#35094

Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>

Not used anywhere, and will be correctly implemented with the
referral application.

Purpose
=======

On a form view, it's possible to add a confirm attribute to open a
popup when clicking on a button.

This mechanism is not implemented on kanban views, and would imply to
create a specific wizard just for that in the referral application.

Coming from the sudo() modification. The mail.message is created in sudo,
but the user is still the public user, who doesn't have a email address,
leading to an raised error.

Previously, success message for promocode was visible only
when user clicked on "I have a promocode". even
when it was successfully applied.

After this commit, message will always appear once a promocode
has been successfully applied.

Task-2027008

closes odoo/odoo#34591

Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>

for easy xpaths

closes odoo/odoo#34909

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

For better rendering

closes odoo/odoo#30629

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>

closes odoo/odoo#35193

Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>