Task Dependencies on the Gantt Chart
Table 75. Availability - Legacy plans
Table 76. Availability
Dependencies specify the relationships between tasks. Use them to indicate when a task should begin or end in relation to other tasks. On the Gantt chart, dependencies appear as lines linking two tasks or linking a task to a milestone.
When you reschedule a task with dependencies, all dependent active tasks are automatically rescheduled. If some tasks in the dependency are completed, canceled, or deferred these tasks are not rescheduled.
There are four types of dependencies you can create in Wrike:
Finish to start: Task B can't start before task A is finished
This type of dependency occurs when the initial task must be completed before the next task can begin. If task A is completed behind schedule, then task B will begin behind schedule as well.
Start to start: Task B can't start before task A starts.
A start-to-start dependency occurs when a secondary task cannot begin until the initial task begins. The two tasks do not have to begin at the same time - task B can begin after task A, so long as task A has started.
Finish to finish: Task B can't finish before task A is finished
A finish-to-finish dependency means the initial task must be completed in order for the following task to be completed. Task A and task B are directly related, and these two tasks may take place at the same time, but task B is contingent on task A.
Start to finish: Task A can't finish before Task B starts
In a start-to-finish dependency, the initial task cannot be finished until the secondary task has begun. However task B does not have to finish at the same time that task A begins.