% Complete jumps to 100%

[jjmclell]

Hi everyone,

We have a task in a schedule that was entered as a fixed-duration task. There are no resources assigned to the task, the task has no predecessors, and no tasks rely on this task as a predecessor.

The duration of the task was set to 25 days. When we went to update the % Complete field for the task from 16% to 40%, Project changed 40% to 100%. 40% also seems to be the threshold for this happening...i.e. if we change the % Complete to 35%, Project keeps it at 35%, but at 40% it bounces to 100%.

Any ideas why this may be happening? I noticed that if we change the task to a fixed unit task type, this doesn't happen. I've been poring over work formula calculations in a guide to MS Project but I'm still stumped.

-jjmclell

 

[JulieInMaine]

Hi,

If there are no resources assigned the task type (fixed units, fixed work, fixed duration) should have no effect. Is the task split in some manner? Usually we only see odd issues with Fixed Duration tasks if there are resources assigned and there is a period of time (trailing split) after the last work that is different from the task finish date.

But, if you have no resources, there should be no work. What do you see if you look at the Task Usage view?

Can you zip and attach the file?

 

[jjmclell]

Hi Julie,

Part of the problem with the project schedule is that it was created by people with no real training in MS Project, and one of the 'project managers' who has been updating the project file from time to time originally entered all of his tasks using Manual Scheduling, without understanding the Project scheduling engine. Since I started working with the team to clean up their schedule, I've had to correct numerous 'legacy' issues related to the way people entered tasks and dates etc. I can't even fathom a guess how this one particular task was entered. Anyways, I would attach a file to show you but I don't feel like signing up for an online storage space...basically if I change the task to fixed units and then back to fixed duration, the problem goes away. I have a feeling it may have something to do with setting the task as fixed duration and then changing the duration of the task...but like I said, in this case, who knows.

Thanks for your post.

-jjmclell

 

[JulieInMaine]

Hi,
I have seen issues with fixed duration tasks and resources assigned who are on vacation. The problem is really when work ends before the end date of the task -- creating a trailing split.

Bear in mind that % complete is a duration measurement -- so changing duration will definitely effect % complete measurements.

Again, without the actual file all I can do is speculate. If setting the task as Fixed Units fixes the oddity, I would suggest setting all tasks as Fixed Units to hopefully ease some of the legacy issues.

Julie