Comment 8 for bug 499645

Hi everybody:

Sorry because I was very late on testing, but I couldn't make it before.

I'm testing in last today's downloaded stable 5.0 bazaar version. I'm sorry but I have to say it is not working at all for me.

Without applying patch and even applying the patch, project_mrp is not working properly now.
On 5.0.6, for each sales order line was created a clean task. On task name was included sales order reference, so you always new the sales order who created task. Since project was not assigned you had to create manually and assign all tasks created for a sales order to same project. I think this is a regression since we are loosing information.

Now... you have no sales order reference on task so you don't know the sales order who created the task. Much more complicated to organize.

1.- Each sales order line creates one task and the task is associated to his own project. So if an order has got 6 different lines, 6 different projects would be created. This is not correct.
2.- If an order has got 2 lines with same product, only in this case both lines are linked to same project.
3.- If 2 different orders have got same product on their lines, both lines are linked to same project. That is totally incorrect, so you are creating projects for products in lines, not for each sales order. Different orders could be from different customers!!
4.- Even with patch applied, project are not linked to an analytic account. Account is not created.
5.- Project name is sales order line product name. This is not correct.

So before, you were able to define manually the project, create the analytic account and assign each task correcty. Now there is a complicated manual operative first to detect wich task is associated to what order... after, relinking all tasks to their projects. Additionally you have to change manually all projects names because they are not correct and you have to create analytic account manually, so... I think this is a critical regression.

Thank you very much:

Ana