Project defaults certain tasks to 100% when a lower percent complete is entered.

Home Forums Discussion Forum Project defaults certain tasks to 100% when a lower percent complete is entered.

Tagged: 

Viewing 15 reply threads
  • Author
    Posts
    • #100359
      Heather Agee
      Member

      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?

    • #100413
      Sarah Kegley
      Guest

      I am also interested in the answer…..

    • #100580
      Heather Agee
      Member

      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.

    • #103461
      ismet kocaman
      Guest

      Heather, Could you pls send me the file at projectuser-at-fastmail.fm ? Thanks. — Ismet

    • #109383
      Heather Agee
      Member

      Ismet, Unfortunately I work on a secure contract and cannot send the file. Thanks for trying to help.

    • #399467
      Ryan Parnow
      Guest

      I have the same problem and Heather’s solution doesn’t seem to fix it.

    • #400291
      Mark
      Guest

      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? TIA

    • #402837
      Howard
      Guest

      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.

      https://social.technet.microsoft.com/Forums/projectserver/en-US/b5899421-8954-47af-b47e-d5ef74a74b48/complete-jumps-to-100?forum=projectprofessional2010general

      • #411217
        Stijn
        Guest

        Thanks, this helps! Still not understanding why this happens, this is a usefull and fast workaround!

      • #494603
        Luis
        Guest

        That approach actually works! Just assure to look for any changes in predecessors/successors, etc. and relationship with other tasks once the change is made. Thanks!

      • #494604
        Luis
        Guest

        That approach actually works fine. Just assure tasks links change(s) after the change. I also document/copied the current % just to play a bit with MS project program to see how it moves while editing. Thanks!

      • #544893
        LLLearning
        Participant

        Thank you so much, @Howard!

    • #410164
      Mark Collette
      Guest

      “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!

    • #411208
      Mark Tallman
      Guest

      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?

    • #411229
      D Robert
      Guest

      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.

    • #411386
      WCH
      Guest

      Worked for me as well.

    • #411412
      Jenn S
      Guest

      Thanks from me as well. Using 2016 and the fix still works. Appreciate it!!

    • #415147
      Dave
      Guest

      Thanks for me too. I was having same problem and the fix worked. I’d like to see Microsoft get this bug fixed.

    • #415779
      RICARDO BRUCE
      Guest

      Well, June 2019 and the bug is still there, luckily the solution above still works. I don’t know how many hours I wasted trying to figure out what I’m doing wrong and find that sometimes the solution is just to close MS Project and open it again, proving that was a bug and not me.

    • #417069
      Figueiredo
      Guest

      Worked for me too! Thanks!

      So guys… can we really assume that this is a BUG in MS Project? Or does someone know if there is a reasonable explanation to MS Project works like this? Thx

Viewing 15 reply threads
  • You must be logged in to reply to this topic.