Dependencies, milestones, and the chain that decides your date
Draw what waits on what, mark the date you're aiming at, and let the board tell you when the order it describes cannot happen.
Until now All Do answered one question very well: who is busy. It could not answer the other one a lead actually loses sleep over — will we make it, and what breaks if this slips. That half shipped this week.
Draw what waits on what
Hover a task bar and two small dots appear just past its ends. Drag from the right-hand one onto the task that waits, and the link is drawn as a line between the two bars. Grab the left-hand dot instead and you are asking the opposite question — what has to happen first? — which produces the same link. Clicking a line removes it, with an undo in case the click was not what you meant.
There is exactly one relationship: this waits for that. No finish-to-start, start-to-start, lead or lag. Those come from construction schedules where they earn their keep; a team of two to ten uses one relationship almost exclusively, and every extra type is another thing to get wrong and another thing to explain.
The board tells you when the order is impossible
Recording the order is the easy half. The useful half is being told when it breaks. If a task is scheduled to start before the work it waits on has finished, the line turns red and dashed, its badge goes red, and the header counts the problem: “2 scheduling issues.” Clicking that steps through them.
Nothing is blocked and nothing is silently corrected. The plan stays editable while it is wrong, and says that it is wrong — because a plan that can be quietly impossible is one people stop trusting.
The same honesty pass changed something you will notice even without dependencies: the blocker badge used to be red on every blocked task. Red now means one thing only, so when you see it, it matters.
When something slips, push the chain
Drag a task later and the board does the arithmetic: “3 dependent tasks now start before this ends — push them.” Accepting moves each one to the first working day after the thing it waits on, around weekends, public holidays, and that person's time off. The whole cascade undoes in a single step.
It is offered rather than applied. Planners that silently reflow your board are ones you end up double-checking every time.
Milestones: something to be on track for
A board could say “on track” without having anything to be on track for. Milestones are the anchor — a release, a demo, a client date — shown as a diamond in a band under the header with a dashed guide down the grid. Drag the diamond to move the date, or nudge it with the arrow keys.
Each milestone reports what unfinished work still lands after it. Scope it to an epic and it counts everything open in that epic; leave it board-wide and it counts only work already in flight across the date, because work that starts after a date was never aimed at it.
The critical path
One optional lens highlights the longest chain of linked work: the only chain where saving a day actually moves the finish date. Shorten anything off it and the project ends on exactly the same day. It is measured in calendar time, so time off and weekends count, and it rests off — it is a question you ask, not a state you live in.
All of it is free, on every board, including the read-only links you share with clients.
Open All Do