On 6 feb, 16:00, Emma <[email protected]> wrote: > Hi everyone, > > I have been using the project module on tryton for a little less than > a month to track time spent on different projects and it works great. > > I have a few new projects that are scheduled ti start soon and I > wanted to use tryton for those projects from conception to billing. > Which led me to questioning the "same parent" restriction on task > predecessors/successors. Let me explain, here is an example of what I > was thinking to manage an MVC dev project > > My project > + Model > | + Product > | | + create (task) > | + Customer > | | + create (task) > | + Order > | | + create (task) > + View > | + Product list > | | + create (task) > | + Product detail > | | + create (task) > | + View cart > | | + create (task) > | + Place order > | | + create (task) > | + Login > | | + create (task) > | + Order list > | | + create (task) > | + Order detail > | | + create (task) > + Controller > | + Catalog > | | + list_all (task) > | | + get_detail (task) > | + User > | | + create (task) > | + Cart > | | + create (task) > + General > + Install database > + Install dependencies > > This is a simplistic approach. Now in order to start my controller => > catalog => list_all task I first have to have completed my model => > product => create task > So in this example, I cannot use the predecessors/followers since > those tasks don't have the same parent, they do have a common ancestor > thou.
This, to me, is solved through network scheduling techniques. I have developed modules in openerp to handle this. Look at : https://launchpad.net/eficent-openerp-project-management The project_time* modules are for managing this. project_scope_wbs is also very interesting for complex projects, as it helps you better navigate through the project work breakdown structure you depicted. > > More over If one of my top projects is "install new server" and > another is "brand new site for new client", in my planning, it's much > better to be done installing (at least some parts of) the new server > before starting to deploy the brand new sites. Those projects don't > even have a common ancestors. > > Please tell me what you think. > > Emma -- [email protected] mailing list
