[15.0][OU-IMP] project: merge project_status

[remytms]

Merge project_status into project module. (https://github.com/OCA/project/issues/1269)

[enricostano]

Hi @remytms ! How can we help to move this forward? Thanks!

cc/ @juanmaGHub

[remytms]

Hi @remytms ! How can we help to move this forward? Thanks!

cc/ @juanmaGHub

@enricostano For me what needs to be done is setting up a migration test process like described by Pedro.

• remove lines from this PR that removes views in pre-migration script
• start from a database in 14.0 with project_status installed and some data.
• migrate from 14.0 to 15.0 with openupgrade
• perform an update all in 15.0 without openupgrade
• migrate from 15.0 to 16.0 with openupgrade
• perform an update all in 16.0 without openupgrade

Each step should work without ERRORS and the data of project_status must be correct in 16.0.

I've not found the time to perform such a test yet. Feel free to do it and report here.

[PicchiSeba]

@remytms @pedrobaeza @enricostano

Hello everyone, I'm in the process of migrating an existing 14.0 installation to 16.0.

I created a test installation with just project_status in order to test this PR. I also included the suggestions given by Pedro (I just commented out the elimination of the views from the migration script).

After the OpenUpgrade step I also upgraded the other modules as suggested. The data is correctly migrated but the second upgrade fails because of an error in this incriminated view

Error: while parsing /opt/odoo/auto/addons/project/views/project_views.xml:552
Error while validating view:

Element '<kanban class="o_kanban_mobile">' cannot be located in parent view

View error context:
{'file': '/opt/odoo/auto/addons/project/views/project_views.xml',
 'line': 2,
 'name': 'project.project.kanban',
 'view': ir.ui.view(525,),
 'view.model': 'project.project',
 'view.parent': ir.ui.view(495,),
 'xmlid': 'project_view_kanban'}

I managed to fix the error by renaming the xmlid of the view to something else. I'm not sure why this fixes the error. The only thing that comes to mind is the fact the views involved have the same xmlid except for the module part.

In our case we might consider actually removing this specific view.