Re: [Tsheetx-developers] Hierarchical task lists

[Jarvis <ja...@jn...>]

Is there any great reason to not add entries against a non terminal 
node? Yes in a classic Gantt chart that's not the right thing to do but 
it simply means that billing something to a non terminal node is just an 
'other' task. It would also mean that a task could be created, have time 
billed to it and then be subdivided into further tasks. Would this be a 
fully implemented Gantt chart or just a way to manage long task lists?

David Thompson wrote:
> This is on the wishlist (see http://bugs.timesheetng.org 
> <http://bugs.timesheetng.org/>), I entered it myself.
>  
> I am not sure that it is so strightforward, but you are right it needs 
> a kind of parent field to support it. You would need to take care 
> that entries are not made against non-terminal (i.e. composite) tasks. 
> In classic Gantt sense their times are the rolled up values of the 
> sub-tasks.
>  
> I don't see any disadvantages of hierarchical tasks, since we have a 
> hierarchy already - flat ;-).
>  
> > Date: Thu, 2 Sep 2010 12:03:26 +0100
> > From: ja...@jn...
> > To: tsh...@li...
> > Subject: [Tsheetx-developers] Hierarchical task lists
> >
> > Would it be possible to make the task lists hierarchical under 
> projects?
> > or would that break anything fundamental in the design?
> >
> > I've been creating projects and entering tasks in the same way that 
> they
> > tend to appear in a gantt chart but a gantt chart is hierarchical
> > whereas the timesheet system doesn't appear to be so.
> >
> > As far as I can see it could be a relatively simple change in the
> > database to add an optional parent task field and a slightly harder
> > change to support the hierarchical tasks in the PHP and HTML but would
> > there be any major disadvantages?