adding propagation of task priority through followers
vijay
tj3 to perform various what-if analysis. e.g. I can have the following
container tasks C1,C2,C3,C4 with each containing a set of sub group
tasks(feature) say T1,T2,T3. Each of T* contains the following leaf
level tasks plan,implement,verify,debug,release.
Now I want to generate reports for various scenarios like.
1> I want the following release schedule Release1 -> Release 2 ->
Release3
2> I want A release schedule having C1.T2 and C4.T3 -> C2 ->C3 and
C4.T1 ->Remaining tasks
3> What if the release schedule was Changed to C3.T1.Verify and
C2.T1.verify and C1.T1.verify ->Remaining Tasks
4> How about All implemented -> All Verified -> All Released
The goal in all these cases is to use taskjuggler to determine the
release dates based on different release criteria.
My original attempt was to define tasks grouped as P{ M{R1,R2,R3} C1
{T1{plan,implement,verify,debug},T2{...},T3{...}} C2{...} C3{...} }
and different milestones with scenario attributes in a separate task
container. My observation was that taskjuggler scheduled the project
such that all the milestones occurred in the last week of the project
I tried to address this with definition of maxend attribute for each
milestone this did not change the scheduling. refering to the manual I
realized that maxend does not affect scheduling. I could use 'end' but
this does not allow all task to finish earlier, pull in the milestone
release and start the next set of tasks
My next hope was specifying priority on each milestone to indicate
that in a given scenario all tasks in the fanin cone of a milestone
should be scheduled first followed by tasks in the fanin cone of the
next milestone and so on. Again this did not have any effect on
scheduling but I saw a patch that was submitted to resolve a similar
issue at http://groups.google.com/group/taskjuggler-dev/browse_frm/thread/6755d3bdb05515fe?tvc=1
While I understand the patch was withdrawn, Is there any plan to
modify this patch and resubmit it in the future?
My end goal is to be able to quickly communicate to my customers the
approx release dates based on different features set selection. Is
there a clean way of doing this without changing the P{...} group of
tasks and their relationship for each scenario?
In case the above writeup is confusing I can writeup a mock plan and
send it across.
Regards
Vijay
Chris Schlaeger
> My next hope was specifying priority on each milestone to indicate
> that in a given scenario all tasks in the fanin cone of a milestone
> should be scheduled first followed by tasks in the fanin cone of the
> next milestone and so on. Again this did not have any effect on
> scheduling but I saw a patch that was submitted to resolve a similar
> issue at http://groups.google.com/group/taskjuggler-dev/browse_frm/thread/6755d3bdb05515fe?tvc=1
> While I understand the patch was withdrawn, Is there any plan to
> modify this patch and resubmit it in the future?
That patch was for TJ2.x and won't work for TJ3.x. But I might have
committed a patch this morning that addresses exactly your scenario.
Please try the latest TJ3 git version and see if it makes any
difference for you.
If not, a small test case definitely helps to understand the situation.
Chris
vijay
I have been trying for the past few weeks to clone from the git repo
without any success. I am planning to rebuild my virtual machine this
month end after which I will be able to test this change.
Thanks and regards
Vijay
On Mar 31, 12:26 am, Chris Schlaeger <cschlae...@gmail.com> wrote:
> On Tue, Mar 30, 2010 at 8:59 PM, vijay <jahagirdar...@gmail.com> wrote:
> > My next hope was specifying priority on each milestone to indicate
> > that in a given scenario all tasks in the fanin cone of a milestone
> > should be scheduled first followed by tasks in the fanin cone of the
> > next milestone and so on. Again this did not have any effect on
> > scheduling but I saw a patch that was submitted to resolve a similar
> > issue athttp://groups.google.com/group/taskjuggler-dev/browse_frm/thread/6755...