This topic contains 13 replies, has 2 voices, and was last updated by Jenn S 11 months ago.
- 03/13/2014 at 8:59 am #100359
On some tasks, but not others, when I enter 90% complete, or 75% complete, or any number besides 0, when I hit enter or move the cursor out of the field, Project automatically changes it to 100% complete. I can’t find the pattern with the tasks that do this – such as how they are set up in the task information window. There is no place where I set it to the 0/100 EV method, it doesn’t seem to matter what task type it is or whether it is marked as “effort driven”, etc. Also this is schedule is not resource loaded. Can you help?03/13/2014 at 3:09 pm #100413
I am also interested in the answer…..03/14/2014 at 7:11 am #100580
Sarah I heard back on this post on Linked In from a colleague and he said, “Zero out the percent complete and then change the duration past the current status date and it should be good to go.” I haven’t tried it yet but I imagine it is probably correct. I’ll let you know next time I come across it.03/25/2014 at 8:05 am #103461
Heather, Could you pls send me the file at projectuser-at-fastmail.fm ? Thanks. — Ismet04/21/2014 at 3:43 pm #109383
Ismet, Unfortunately I work on a secure contract and cannot send the file. Thanks for trying to help.06/28/2016 at 3:13 pm #399467
I have the same problem and Heather’s solution doesn’t seem to fix it.07/14/2016 at 11:11 am #400291
I have this same issue and I deleted everything I could and it still has the same error. I first thought it was an issue with the resources being overtasked, but I even deleted all of the resources and it still had the same error. Anyone have any ideas? TIA09/09/2016 at 12:20 pm #402837
I found this description of why the problem occurs. I was able to resolve the issue by setting the duration to 1 day, then changing the task type from “Fixed Duration” to “Fixed Units” then back to “Fixed Duration”. I then set the duration of the task back to the real duration.06/02/2017 at 9:31 am #410164
“Howard”, thank you, I tried the steps you listed and it worked, I don’t know why – but as long as it worked I am happy, thank you!11/14/2017 at 4:52 pm #411208
Correct me if I am wrong, but does anyone really think we should have to jump through rings of fire to make something work that should simply just work? I don’t know about anyone here, but I am sick and tired of endless Microsoft bugs. Anyone else? Bueller?11/15/2017 at 8:14 am #411217
Thanks, this helps! Still not understanding why this happens, this is a usefull and fast workaround!11/16/2017 at 10:21 am #411229
I just encountered the same issue in MS Project Standard 2013. Using Howard’s suggestion, the issue was resolved. However, changing from “Fixed Duration” and back again was not necessary.12/12/2017 at 5:43 pm #411386
Worked for me as well.12/13/2017 at 4:39 pm #411412
Thanks from me as well. Using 2016 and the fix still works. Appreciate it!!