I've filed a bug report for the issue.
I have a project (my Son's not inconsiderable homework diary) that OP is the ideal tool for.
What I was doing:
For each item of homework I'd have a milestone representing when it must be handed in. To that I'd wire a work task scheduled ALAP (of course!). This worked fine but meant two tasks (the work and the milestone) for each piece of homework and some wiring to do. A little too much data entry work for my liking.
What I want to do:
Simply have a single task for each piece of homework where the due date is the end constraint for each task. Then there'd be only one task to enter per piece of HW, no wiring and the plan would be easier to read.
I did discover that it's not just the last task that's affected by the issue, it can cause other problems that disappear if tasks are needlessly wired together.
Quote:
Originally Posted by whpalmer4
It looks to me like that constraint needs something to "push against".
|
It certainly looks that way.
I guess, this is probably a mode of use people don't use much - tasks a usually wired together with a milestone at the end.