Task Dependencies Setup (Gantt Chart) in Bitrix24
The designer delivered the mockup, but the developer didn't know — the markup task was still waiting. Or the opposite: the developer started markup before mockup approval and redid it twice. Without dependencies between tasks, everyone works in a vacuum and the manager spends time on manual coordination. Gantt chart and task dependencies in Bitrix24 solve this: tasks are linked into chains, shifting one automatically shifts the rest.
Types of Dependencies
Bitrix24 supports task dependencies through "previous task" binding. The main type is Finish-to-Start (FS): task B starts after task A completes.
Chain examples:
- "Approve specification" → "Design mockup" → "Markup layout" → "Test"
- "Approve budget" → "Purchase equipment" → "Install equipment"
A link is set in the task card: Previous Task field. One task can depend on multiple predecessors — it starts when all predecessors complete.
Gantt Chart
Gantt is a visual representation of project tasks on a timeline. Each task is a horizontal bar whose length corresponds to duration (from start date to deadline). Dependencies are shown as arrows between bars.
Access: Tasks → Project → "Gantt Chart" view (view switcher next to Kanban and list).
On the chart you see:
- Task sequence — which run parallel, which sequential.
- Critical path — the longest chain of dependent tasks, determining minimum project duration. If a task on the critical path is delayed — the whole project shifts.
- Overloads — if one person is assigned to two parallel tasks, it's visible on the timeline.
Automatic Deadline Shifting
When a predecessor task shifts — dependent tasks shift automatically. This works forward along the chain: shift "Approve Spec" 3 days → "Design Mockup" shifts 3 days → and so on down the chain.
Shifting works only for tasks with set start and end dates. If a task has no deadline — dependency won't work correctly.
Milestones
A milestone is a task with zero duration, marking a key project event: "MVP Release," "Contract Signed," "Campaign Launch." On the Gantt chart, a milestone appears as a diamond.
A milestone serves as a control point: if all preceding tasks complete on time — milestone stays in place. If even one task is delayed — milestone shifts, signaling the manager.
Working with Gantt in Practice
Workflow with the chart:
- Project decomposition — break into tasks 1–5 days long. Tasks longer than a week are too large to manage.
- Establish dependencies — determine what follows what.
- Assign owners and deadlines — accounting for dependencies.
- Track execution — daily or at standups. Shifts on Gantt are immediately visible.
- Adjust the plan — when deadlines change, recalculate dependent tasks.
What We Configure
- Project structure: decomposition into tasks and subtasks
- Dependencies: task links (Finish-to-Start)
- Milestones: key project control points
- Gantt chart display setup in the project
- Manager training: reading critical path, managing shifts
- Task sizing and planning recommendations accounting for dependencies