On 02/06/2012 04:00 PM, Emma wrote:
>
> 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
[tree cut]
> 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 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.
> 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.
You could use the relaxed restrictions on predecessors/successors, but I
get the feeling this more like milestones: sets of tasks or sub-projects
from possibly disparate projects whose completion denotes a marked phase
transition even when the respective parent projects are not completed.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin
* Premium Hosting Services and Web Application Consultancy *
www.nfg.nl/[email protected]/+31.85.877.99.97
________________________________________________________________
--
[email protected] mailing list
