Behavior prior to the fix:

- when adding a filter on "Quantity < 0" (or > 0) on the forecast
inventory report the quantity reported becomes incorrect: for example if
there is a restock on Tuesday and a shipment on Friday that drives the
forecasted quantity into a negative, the forecasted inventory report
instead reports a negative quantity on Monday.
- the problem occurs because the view the report is based on is built
using positive and negative entries that are supposed to cancel each
other when accounting for stock items (quant).  This way the quantity is
reported as 0 before the quant is moved in the inventory (there is a
positive entry for the quant, and a negative entry for the move up to
the move effective date).  But when a filter on quantity is placed the
"cancelling" entries are not loaded and the report ends up with just the
negative value

Behavior after the fix:

- the quantities are reported as expected: with a negative on Friday,
and 0 on the days before
- to achieve this the view was modified to perform the grouping of
forecast entries inside of the view.  This way we have one row per
product / day / state and we don't risk selecting only part of the
report.
- as the view is only read in aggregate there will not be any visible
changes to its consumers

opw-2379098



--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#62457
Forward-Port-Of: odoo/odoo#62064

### Goal of the PR
This PR is mainly a revert to 13 functionalities in project_* modules as functional changes introduced in 14 do not seem to be well accepted by users.

### Details

- sale_timesheet: rename 'Ordered quantities' service_policy into 'Prepaid'
- project, sale_project, sale_timesheet: refactor task form view
- sale_timesheet: modify sale_line_employee_ids many2one widget on project form
- sale_timesheet: add link between ticket and sale order
- sale_timesheet: remove the option 'link to an existing SOL'
- sale_timesheet: remove the warning messages in project.task
- sale_timesheet: reword labels in customer_type and pricing
- sale_timesheet: adapt timesheet section on invoices in portal
- sale_timesheet: add timesheet section on orders in portal
- sale_timesheet: remove employee rate related warning on projects in Kanban view
- sale_timesheet: update sale_line_id of all the not invoiced timesheets accordingly to the employee mappings
- sale_timesheet: timesheet entries for employees that have no mapped SOL in project get the sol of the task or project

task-2388500

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#62360

This commit forces the default value of the mail.mail 'state' field to
'outgoing' (the default field value), when notifying the record by email.

Without this change, there can be a collision when the ORM tries to compute
default values for this state field. For example:
- Model "A" has a 'state' field ;
- Create an action that redirects to model "A" form view, setting some default
  values in the context such as {'default_state': 'done'} ;
- Model "A" has an inherit on 'mail.thread' and a 'user_id' field to set a
  responsible user ;
- Model "A" record is created with a responsible user, who is automatically
  notified by email that the record "has been assigned to him" ;
  (see mail_thread#_message_auto_subscribe_notify)
- A 'mail.mail' is in turn created ;
- The 'mail.mail' model ALSO has a 'state' field, and the context is propagated
  so the ORM will try to assign 'done' to that field, which is an incorrect
  value ;
- -> Crash.

If we ensure that the value of the state is set to 'outgoing' for that record,
we bypass the default values computation for the 'state' field and everything
works fine.

A test was added to make sure this works properly.

Task 2393259

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#62545
Forward-Port-Of: odoo/odoo#62339

Issue

	- Install Sales
	- In Sales > Configuration > Settings -> Enable "Sale Warnings"
	- Go to Sales > Orders > Customers
	- Pick a customer/company
	- Go in Edit mode and go to "Internal Notes" tab
	- Switch "Warning on the Sales Order" from "No Message" to "Warning" and add any warning message then save
	- Press the "$ X Sales" smart button
	- Create a new Quotation
	- Validate the warning message
	- Go back to the previous menu (using the breadcrumb) or save the quotation
	- Create a new quotation

	The quotation form editor does not appear.

Cause

	If we use the breadcrumb (or save then create), it will call the `_reload` function
	(instead of `load` when the form view hasn't been opened yet).
	In this case, creating a new record, it will call `_makeDefaultRecord` without
	setting `allowWarning` param to true (like it is done in the ref. commit bellow).

Solution

	Set `allowWarning` param to true before calling `_makeDefaultRecord`.

related commit : https://github.com/odoo/odoo/commit/a41db9a2cf410bb233b021651a5633180eaddf18

opw-2374857

Forward-Port-Of: odoo/odoo#62534
Forward-Port-Of: odoo/odoo#62204

## Helpdesk

- (helpdesk_timesheet,helpdesk_sale_timesheet) allow_billable=True when use_helpdesk_sale_timesheet=True: Before this PR, when the user checks the 'time reinvoicing' and saves in helpdesk.team, if the helpdesk_sale_timesheet is not installed, the generated project will not contain the allow_billable set to True. Because the generation of this project is made in **_init_data_create_project** method when helpdesk_timesheet is loaded or in write method of helpdesk.team defined in helpdesk_timesheet module. In this PR, we add  **_post_init_hook** in helpdesk_timesheet and helpdesk_sale_timesheet modules to generate project in helpdesk.team in the last module installed (case when the user checks 'Time Reinvoicing'
and 'Timesheet on Ticket'). If the user checks only 'Timesheet on Ticket' and saves the project has right generated with allow_billable=False. After that, if the user checks 'Time Reinvoicing', then we set the allow_billable in this generated project to True.
- (helpdesk_sale_timesheet) Update the creation of the sale order in ticket: Before this PR, we can create a sale order, if the allow_billable in the project linked in the ticket is set to False. Because, before the allow_billable=False means the pricing type is equal to "Task rate". But now it's not the case, it means that the project can't be invoiced. Moreover, when the user wants to create a sale order from a ticket in which the pricing type is equal to "project rate" or "employee rate" in the project linked, then the quantity in the first sale order line stay to 0. It's because the ticket is not linked to a task and then the timesheet is not linked in the first sale order line of the sale order created. In this PR, we change the condition for the visibility of the "create sale order" button to fit with the configuration of the project linked to the ticket. And we add a context key called "timesheets_on_ticket" to give the timesheets in the ticket to the wizard for the creation of the sale order. With this key, if the project in the ticket does not contain a task then the timesheets in the ticket are correctly linked in the first sale order line of the new sale order.
- (helpdesk_sale) Hide the sale_order_id field in form view of ticket.
- helpdesk_timesheet: Remove the warning messages in ticket: When the user changes the task of a ticket in Helpdesk App. We displayed a warning message about the impact of this changes. This warning message was useful to inform the user that is a change in the behaviour compared to the previous version of Odoo. But each time, the warning message appears and it can be boring for the user. That's why we remove the warning message.
- (helpdesk_sale_timesheet) Add stat button in ticket: we add a stat button in form view of helpdesk.ticket model. This button allows the user to see the sale order linked with the current ticket. This button only appears if the user has the group_sale_salesman group **and** use_helpdesk_sale_timesheet=True in helpdesk_team **and** it exists a sale order linked in the current ticket.

## Field Services

- (industry_fsm_sale): invert allow_quotations default logic: that is, we want this button will appears only for the fsm projects only by default.
- (industry_fsm and industry_fsm_sale): refactor task form view: 
    - we change the visibility of the phone field, this field is visible if is_fsm is True.
    - we hide the sale_line_id field when allow_billable is False or is_fsm is True.
- (industry_fsm_sale) Hide sale order in task if non billable: When the allow_billable=False in the fsm project, we should not see the sale order in the form view of project.task as it's the case for the sale order line field in the same model.
- (industry_fsm_sale) Prevent the user to configure fsm project with employee_rate or project_rate: Indeed, the fsm project doesn't correctly work to create sale order when it is configured as project_rate or employee_rate. That's why this commit allows only to configure a fsm project with task rate. Moreover, when the user creates or updates a project to have a fsm project, we need to be sure that the sale_line_id field in project is not set to respect the sql_constraint.
- (industry_fsm_sale) Hide Sale Order if the project is not fsm project: we hide this field in the form view of project.task.
- (industry_fsm_sale) Sale Order can just be selected in task of fsm project.
- (industry_fsm_sale) Display the 'New Quotation' button: If the user disables the feature in the settings of Field Services, that is 'Extra Quotations' (correponds to group_industry_fsm_quotations field) then the button 'new quotation' is always displayed for fsm project because the allow_quotations in the project is set to True. Since the group_industry_fsm_quotations field implies a group named 'industry_fsm_sale.group_fsm_quotation_from_task', we add this group in the groups attribute of the button and check the user has the group in the compute method of allow_quotation field to fix this problem.
- (industry_fsm_sale) sale_line_id visibility does not depend on sale_order_id in project.
 
task-2388500

Forward-Port-Of: odoo/enterprise#15025