- aligned Edit Quote and Print buttons
- changed button string from "Update Quote" to "Edit Quote"

Project form view: some cleaning in the settings tab (use technical group, put
timing fields on the group_time_work_estimation_tasks).
Light cleaning of the tasks form view.
Light cleaning of the issues form view.

project_timesheet: timing fields put in gorup_time_work_estimation_tasks group to
be coherent with previous changes.

concept of default / common stages.

However as the link between stages and projects is still a many2many
it is still possible to have shared columns. It is however not the
standard way of using stages.

Members were not used in project, except for the now removed faces library.
Statistics can still be computed based on task or issues responsibles
instead of adding all members of a project.

Indeed you could have members that did not actually work in the project
making it difficult to differentiate with followers. Now the concept
of members is removed. Followers is sufficient for communication.

Change is not retroactive to avoid breaking existing translations.
Courtesy of nmi.

Not comprehensible or wrong terms.
Courtesy of @rim-odoo

[IMP] account: moved analytic checkbox on taxes to the right column of the advanced options under the other checkboxes

This change is meaningless in community but was required for the enterprise
edition has the way to scroll the webclient just changed from triggering an
event on core.bus to triggering_up the custom_event 'scrollTo'.

for widgets that don't use it, instead of hidding it directly. Doing so, the
control panel is hidden simultaneously with the old view, and there is no more
flickering.

only if the control panel if visible.

This fixes a bug on the settings view (form view), on which the control panel
is hidden (the bar containing 'Apply' and 'Cancel' is unfortunately not a true
control panel). When clicking on 'Apply', for some weird reason, the event
'change:title' is triggered and the control panel is updated with the new title
('New'). However, as the flags hidden isn't mentionned, the control panel
visibility is toggled.

The event dialog in calendar showed the event name as title and
repeated the information in its content

Title fields were not correctly aligned in enterprise version

aliases explanation and redirection to the general settings.

Added an option to automatically generate an alias for sales
teams, like what is done in projects.

Some cleaning has been done in the form view. Aliases are
valable only for sales team managing leads.

organized pipeline with the new organization and views.

[REM] crm: removed unused file crm_report_view.xml, containing
strange old views, probably some old reports. Those seems to be replaced by
the opportunities and activities analysis + the various dashboards and
graph views.

Stages are now sales team dependant, and not shared anymore. This comes
with a sales-team way of working :
- sales team is the entrance point, click on the big Pipeline button to
see the opportunities pipeline of this specific sales team
- no more opportunities menu entry, as you should come from a sales team
- leads are still sales-team agnostic

The stage management has been updated :
- Won is still a stage (probability=100, onchange=1).
- Lost is not a stage anymore. Lost is equivalent to archiving. Archiving
uses the active field. Setting a lead or an opportunity as lost set them
as unactive.

Downside of the no more share policy: multi sales team opportunities
management can quickly become complicated. Indeed you may have stages
with the same name, not being the same stage, therefore not displayed
in the same column. Grouping on the stage name leads to other issues
(sequencing incoherence, impossible to drag n drop), so this is not
an option.

its views in its own file. Just reorganizing things before cleaning
a bit.

Using several sales team and the new dashboards is now the only
behavior about sales team. The unique sales team mode is therefore
removed, leading to some update in the various addons that hide
the team_id field when not in multi sales team mode.

[DEMO] cleaned demo data (removed marketing sales team because it should
not exist)

[FIX] crm: assign date_open in leads only if not set in the values.
Given values have the priority on default-like values.

of unactive records. The chatter now uses a correct read_ids (no need
to have a search set), with an active_test in the context allowing
to read on unactive records.

otherwise it is not correctly computed on new records inheriting
from mail.alias class.

This avoids breaking shortcuts on Firefox, which rely on keypress
events instead of keydown / keyup. The tradeoff is that a barcode
cannot be scanned and interpreted if ctrl, alt or cmd is pressed.
Also don't catch function keys.

BarcodeEvents uses the fact that a barcode usually ends with \n, \r or
\t - and never contains it - to stop buffing keys as soon as such a
character is inputted instead of waiting x milliseconds.

This functionality was an attemps to fix the chair-to-keyboard
interface in the PoS. Since it is not a standard behaviour, it
must be explicitly requested.

In order to remove an eventhandler, removeEventListener must receive
the same function reference that was passed to addEventListener. So
the handlers references are kept as attributes of the class.

If the module barcodes is installed, a BarcodeEvents singleton is
automatically instanciated. It listens to keypresses and, when a
sequence of keys represents a barcode, it broadcasts a 'barcode_scanned'
event on core.bus containing the barcode string.

deprecated use oauth2 instead

- Remove domain (only search context)
- Set correct default values for both template and variant when creating a bom
  when coming from a product variant from

- Reorder views per model and per actions
- Remove dead views and actions
- Flatten configuration menu, only the resource submenu is kept
- Rename mrp_bom_tree_view to mrp_bom_line_tree_view (no other xmlids where harmed in this commit)
- Add a view mrp_bom_tree_view for bom list with name and product variant when group_product_variant is enabled

[IMP] Creation  date is confusing since its not the creation date in order point with po lead times. And user want the scheduled date rather than the creation one

[FIX] Scheduling of orderpoint: it was wrong to add the supplier lead time at every rocurment (what do you do if you manufature) and wrong for PO: you were always late

This causes issues when people delete the Website Sales team. The
website_sale module already adds a salesteam_id to website, which is
configurable. So instead set that to website.salesteam_website_sales by
default and use it in both website_sale and website_crm.