P
Peter
I have a task that has the following attributes:
Fixed work (effort driven)
A predecor or a milestone task (so no resource assoicated with the pred task)
no other linked tasks
A resource assigned with plenty of availblity - no over allocation
Situation:
The task had a constain of "Start no ealier than" and a start date somewhere
months ahead so the time between milestone end and task start is significant.
I changed the attribute of the task to "Start as soon as possible" thinking
that it would collapse this time.
The result is no matter how matter what I do to try and change the start
date of this task it will not take - period. There is nothing indicating
that the Resource is causing this odd restriction.
There is one oddity: out of desparation I changed the attribute of the task
to "Must Start On" and a Link warning popped up. What is off is that there
are no more links to this task - period.
Did I just run into a corrupt piece of data?
Do have to rebuild the task (delete and re-add it from scratch)?
Why is this occuring? Any know bugs out there regarding this?
Fixed work (effort driven)
A predecor or a milestone task (so no resource assoicated with the pred task)
no other linked tasks
A resource assigned with plenty of availblity - no over allocation
Situation:
The task had a constain of "Start no ealier than" and a start date somewhere
months ahead so the time between milestone end and task start is significant.
I changed the attribute of the task to "Start as soon as possible" thinking
that it would collapse this time.
The result is no matter how matter what I do to try and change the start
date of this task it will not take - period. There is nothing indicating
that the Resource is causing this odd restriction.
There is one oddity: out of desparation I changed the attribute of the task
to "Must Start On" and a Link warning popped up. What is off is that there
are no more links to this task - period.
Did I just run into a corrupt piece of data?
Do have to rebuild the task (delete and re-add it from scratch)?
Why is this occuring? Any know bugs out there regarding this?