Your project roadmap, finally on a timeline
Two facts that never met: the task running late, and the work waiting on it. The new Dependencies tab puts them on the same timeline, so the clash is a red line you see coming.
The UnaTask team, Building UnaTask. Jul 6, 2026. 4 min read.
It is Tuesday. The designer pings you with a simple question: is the API ready, because she cannot build the screen without it. You go and check. The API task says in progress, due next week. Her design was due yesterday. Two facts about the same project, and somewhere between two different lists, they never met.
This is how projects slip. Not with a bang, but with a small silence between a task and the thing waiting on it. Nobody was careless. The dependency was real, everybody sort of knew it, and still it lived in someone’s head instead of somewhere you could point at. By the time it surfaces the calendar has already moved, and the standup gets a little quieter than usual.
So we built a place where those two facts meet. There is a new Dependencies tab in every project, and it lays your tasks out on a timeline.
What it looks like
Each task is a card, floating on a date axis. Where a card sits, left to right, is when it happens. The lines between cards are dependencies: this one has to finish before that one can start. You draw one by pulling from a card toward the task it depends on, and the link appears.
Drag a card and it moves in time. Drag its edges and it takes longer or shorter, right there on the axis, so a two day task and a two week task look like what they are. It reads like a plan because it is one, not a list pretending to be a schedule.
When the plan changes, everything downstream moves
Here is the part we are proud of. Stretch a task so it runs a few days longer, and everything that depends on it slides forward on its own. You do not chase the knock on effects, the timeline does. When you have trimmed things back down and want the plan tight again, one button, Recompact, pulls every task back against the thing it was waiting on.
And when a plan does not add up, you see it. If a task that blocks another one ends after that other one is meant to start, the line between them turns red. The hidden delay stops being hidden. It is a red line pointing at the exact place the week is about to break, a week before it breaks.
Add a task by just typing it
You do not fill in a form to get here. Click any empty spot on the timeline and type the task the way you would say it. Draft homepage tomorrow, assign it to Sofia, mark it high. It reads the date, the person and the priority as you write, shows you what it understood, and drops the task exactly where you clicked. Click any card later and you can change everything about it, status, people, dates, estimate, without ever leaving the canvas.
A plan you can see is a plan you can trust.
The same Tuesday, a week earlier
Now run that Tuesday again. A week before the designer pings you, the line between the API and her screen is already red on the timeline. You move one of them a few days, the red goes away, and the conversation you were going to have on Tuesday simply never needs to happen.
That is the whole idea. Dependencies were always there in your projects, quietly deciding what could happen and when. We just put them somewhere you can see them, on the same timeline as the work, so the plan stays honest and the surprises get boring. Open any project, tab over to Dependencies, and pull your first wire.