Dependencies

A dependency means this task waits for that work to finish. The waiting task starts as soon as its predecessor is done: same day if hours are left, next working day if not.

What you can wait on

• Any task, in this group, another group, or another work stream.
• A group, which means waiting for every task inside it.
• Cross-work-stream waits are first class. A dependency living in another work stream carries a work-stream badge on its chip in the task sidebar, so you always know where it lives.
• Loops are prevented at the door. The picker will not let you wait on your own group, or on any task that already waits on you, directly or through a group link. The greyed rows say why.

Setting them

Open the dependency picker from a task's sidebar (+ dep) or the After column. It is the same indented tree as the planner: tasks nested under their groups, in order.

Check a task to wait for it, uncheck to stop; the picker adds and removes in one save. Prefer clicking? Choose Pick from chart and click the rows on the Gantt.

If your task's group already waits for another group, picking a single task inside that group shows a note: it is already covered by the group link, so the finer one will not change any dates. Fine to do, just worth knowing.

Chain a whole group at once

Right-click a group and choose Chain tasks sequentially to make each task wait for the one above it, in order. Existing dependencies are kept, the sequential links are added on top, and the whole thing is undoable.

What happens to a date you typed

A predecessor overrides the start date on the waiting task. Your date is not thrown away: it is kept and ignored while the link exists, and it comes back the moment you remove the link.

Put it at the right level

"All of Paint follows all of Weld" is one dependency, group to group. "The test follows this one weld" is task to task.