Skip to main content
Question

When I use predescessors on a task, it does not auto-populate the start date based on the previous task's completion date. I'm wondering if this is a setting that might have been turned off and I don't know how to turn it back on? Any suggestions?

  • September 11, 2013
  • 0 replies
  • 75 views

When I use predescessors on a task, it does not auto-populate the start date based on the previous task's completion date. I'm wondering if this is a setting that might have been turned off and I don't know how to turn it back on? Any suggestions?
This topic has been closed for replies.

Forum|alt.badge.img+12
  • Registered
  • September 12, 2013
Check your "Predecessor" field is properly setup and actually references a Start Date and a Duration

  • Author
  • Registered
  • September 13, 2013
And the Start Date is a Work Date

  • Author
  • Registered
  • September 13, 2013
Yes, it does reference a start date, and a duration.

Forum|alt.badge.img+12
  • Registered
  • September 13, 2013
I would probably need to see it - can you contact me offline so we can try to resolve?

  • Registered
  • September 18, 2013
What was the resolution to this? I am having the same issue.

  • Author
  • Registered
  • September 18, 2013
I had to get Quickbase Support involved.  They're currently working on a resolution, but have not fixed it yet.

  • Registered
  • September 30, 2013
also, make sure you're tasks are linked to "Work Dates" and not just a regular date field.

  • Registered
  • September 30, 2013
Great - thanks Erica. That's what I suspected based on some other threads I've seen. I hope they get this worked out, it's pretty critical for scheduling.

  • Author
  • Registered
  • October 2, 2013
Thanks for weighing in.  They are Work Dates.  Quickbase has still not provided a solution.

  • Author
  • Registered
  • December 17, 2013
for anyone following this thread - the predecessors field was corrupted.  I don't know if it was on our application alone, or all applications up to a certain point.  I had to delete the field, and create it again.

  • Registered
  • July 8, 2019
Looks like this is still happening. I had the same problem and used your advice to delete the Predecessor field and create it again.