Sorry for the late reply... > This can be solved for you by creating a small custom module that will > modify the predecessors and successors fields to relay the restriction > currently in place. Looks trivial enough.
Yes, this is what I did, I was just wondering what everyone else thought about it :) > I think the issue is because the project_plan uses the concept of > milestone and Emma did not split the project in milestone but in "kind > of work". Yes, the idea behind splittind the project into "kind of works" is to be able to use Tryton from scratch on a new project. I thought of using the (sub)project description field as an analytical repository for both developpers and client. Developpers can check what is exactly expected and I'm planning on a custom report that could be printed and signed by the client based on the tryton project. Maybe the "project" in this particular scenario is actually a milestone... > Perhaps we miss an other concept which allow to group project task in an > other tree structure for business vision etc. A little bit like the idea > of consolidation in accounting. Yes, I guess this would be a good idea, maybe a module called project_business or project_analytics which would allow to group works of a parent project into different categories/groups ? Emma -- [email protected] mailing list
