Is there a way to account for elapsed time in predecessors when lag is added?

Katy H

My team was relieved when we discovered that elapsed time was available for duration in projects. I manage a project tracking process that goes from plant cultivation all the way to packaging. All of our cultivation processes use elapsed time while the rest of the project follows regular working days. One of the cultivation processes has a lag of 4 days after its predecessor. But that negates the elapsed time duration and puts it back to working days. Has anyone found a workaround for this?

Julio S.

Hi @Katy H ,

As you point, predecessors are based on the duration formatting (working days vs elapsed time) of the row they are at, not the preceding one. If the predecessor is in a row where elapsed time isn't used, the lag time will add to working days duration even if the previous row used elapsed time. If you'd like to have the ability to adjust lag time to elapsed time instead even if the row duration doesn't is calculated in working days, when you have a moment, please let our Product team know about your feedback by filling in this form, here. Thank you! 

For the time being, my advise would be to manually adjust lag time depending on which day the predecessor ends. For example, if cultivation ends on a Saturday and your working week runs from Monday to Friday, you may use a lag of 2 days instead of 4. 

I hope this can be of help. 

Cheers! 

Julio