[tbrekken]

I have observed the following:

If I have a task for which there are no workers assigned, then the lead time to a subsequent task works the way it should. If I set a lead time of 1w between two dependent tasks, then the arrow linking the two extends out for one week before connecting to the dependent task.

However, if I assign a worker (resource) to the first task and that worker does not have a 8 hour/day work schedule, then the lead time mysteriously scales as a function of the number of hours that resource can work. For example, if I put a lead time of 1 day between two tasks, and the first task has a worker assigned to it that works 1 hour per day, then the lead time to the next task will extend out for 8 days.

Is this a bug? If not, how do I get the lead time to be "absolute" lead time?

Thanks!

[skwirl]

Originally Posted by tbrekken

I have observed the following:

If I have a task for which there are no workers assigned, then the lead time to a subsequent task works the way it should. If I set a lead time of 1w between two dependent tasks, then the arrow linking the two extends out for one week before connecting to the dependent task.

However, if I assign a worker (resource) to the first task and that worker does not have a 8 hour/day work schedule, then the lead time mysteriously scales as a function of the number of hours that resource can work. For example, if I put a lead time of 1 day between two tasks, and the first task has a worker assigned to it that works 1 hour per day, then the lead time to the next task will extend out for 8 days.

Is this a bug? If not, how do I get the lead time to be "absolute" lead time?

Thanks!

Hmm, not sure if this is a bug, but I can see how it could be confusing to users who are expecting a different behavior. I'll file a bug report with your findings and we'll check this out ASAP.

Thanks!