Code review comment for lp:~akretion-team/project-service/add-project-action-item

Hello Daniel,

I just want t mention that yesterday I talked with Alexis and I spontaneously made exactly the same remark as you with the concept of children tasks instead of that new actions object.

There are several modules trying to fix the need for a standard Workbench Breakdown Structure (WBS from PMI) in OpenERP.

Ferdinand Gassauer at C2C2 maintained a parent-child task hierarchy module for years (not remembering the link though) and there is also this project_scope_wbs PMI WBS module from Efficient now that would eventually be interesting to bring into OCA:
http://bazaar.launchpad.net/~eficent/eficent-openerp-project-management/7.0/files

On our side at Akretion we will also soon push an other module called project_feature that also aim at managing different granularity scales for projects, this time bridging operational tasks with the customer metric expressed with a new object called project.feature.

So there is definitely effort in that direction and we should avoid "leaky abstraction". That is as you said, if with minimum effort would could make it work with a hierarchy instead of introducing that action object, that would be cool.

If that is not possible, we should try to make it at least compatible with the modules trying to bring WBS hierarchy.

All in all, this module seems great, but we should double check if we can make the most of it before blessing it to OCA.

Regards