Mysterious Date Changes... Dependencies and edays?

Akblevins

Hello,

I've had a few users reach out to me today about seeing changes to their project plans, but no one went in to change dates. The activity log was clear of anyone specifically doing anything to affect the start and end dates.

The recent user, after investigating her plan, had a predecessor (our dependency column) that looked at an above row and was to start 7 days after that line finished. The start day of this successor row was 2 days after the completion of the predecessor.

We think that with the lag time in the predecessor in conjunction with the e9d duration that something isn't jiving well. The e-days shouldn't affect the start date, only the duration of the activity itself. As you can see the next activity has the predecessor with no lag/lead times and e-days in the duration but did not affect the start date.

Here are the project settings if anyone is curious, as I thought maybe it was a settings issue:

Anyone else experiencing this or have a solution as to why all of a sudden this has changed dates within a project? These dates haven't been touched since 2024/2025

Georgie

Hi @Akblevins,

Thanks for sharing the screenshots! 

I can see that your project settings are already set up with working days as Monday to Friday. Predecessors are set based on the project settings, so are already accounting for weekends as non-working days. 

It’s not possible to add elapsed time into the predecessor column, and you can use either elapsed time in the duration column OR lag time in the predecessor column - but you can’t use both at the same time. Take a look at this related Community thread for more information.

Please also add your vote and comment to this product idea:

• Elapsed Days in Predecessor Field

Thanks,

Georgie