sale_project: migration to 18.0 change in field selection logic of task_in_project

[sergiocorato]

Module

sale_project migration

Describe the bug

In v. 17.0 selection of field service_tracking with task_in_project created a task in the existing project of the sale order.
In v. 18.0 the same selection create a new project and a task inside it, even if the project in set in sale order.

To Reproduce

Affected versions:

• 18.0 [18.0][OU-FIX] sale_project: service_tracking selection logic has changed #5994

Steps to reproduce the behavior:

1. create a sale order with a service with service_tracking with task_in_project
2. set the project in the sale order
3. confirm the sale order

Expected behavior
A task is created in selected project

Additional context
The placeholder in the selection task_global_project says Defined on quotation, which is correct for that selection: https://github.com/odoo/odoo/blob/238a41e35280256382f6509182b9e900fb4f7aba/addons/sale_project/views/product_views.xml#L19
Test other selection usability.

[pedrobaeza]

So is there something to change in the scripts?

[sergiocorato]

task_in_project:

• <= v.17 create a task in sale order and create project if not set
• v.18 and v.19 create a task in sale order and a new project, even if project is set in sale order
  To do the same thing as before, change this value to task_global_project and leave project empty in the product.

task_global_project:

• <= v.17 create a task in sale order in the project set in the product
• v.18 and v.19 it does the same

@pedrobaeza so the idea is to change in the migration the value from task_in_project to task_global_project

[sergiocorato]

Additional todo: update translations with new logic

[pedrobaeza]

Closing as there's a PR. Please don't open two things, as it spreads information across them.