Quote:
Originally Posted by aboeing
I found the solution of adjusting constraints to be buggy - adjusting your system clock works every time.
|
I wasn't proposing adjusting constraints, but removing them. If you aren't getting the result you expect when you remove the constraint, it's likely that there is some other reason why OmniPlan is scheduling the task when it does. Resource availability, priority, position in the document, dependencies, and project calendar all affect the leveling/scheduling process.
Remember that the constraint put in when you add actions is a starting constraint, not an ending one, and simply means that the action will not be scheduled before that date/time. It does not mean that the action will be schedule AT that date/time.
There's nothing that guarantees that a plan fiddled with by adjusting the date when you put in earlier actions will stay the way you want if you continue to change the plan. A better practice would be to eliminate the constraint, then set the start date and lock it.