The Auto-scheduling is a powerful feature to save a lot of time to plan the tasks automatically. It This feature is done applied only on Auto-Scheduled issues in two steps based through the following order :

Flat Dependency Scheduling

This is a simple and classic dependency scheduling: the scheduling of issues through dependency links. The issues are not container issues.

In this example, all issues are auto-scheduled. The current date is used as start time of the first issue in the chain.

If there is a Manual-Scheduled issue on the chain, its Start and End times will be used to schedule the issues linked before and after. The selected issue in the following gantt-chart is Manual-Scheduled.

Flat Resource Scheduling

The Auto-Scheduled issues without any dependency are known as isolated issues. The scheduling is done separately in each group per assigned User. The following Gantt-chart contains two groups:

Container Dependency Scheduling

This dependency scheduling supports container issues. Using the previous sample, the following example turns a simple Auto-Scheduled issue to a container issue "Shipping" by adding two sub-tasks. The container remains auto-scheduled.

Dependency Sub-task Scheduling

Here is the gantt-chart when the sub-tasks are linked in Start/End dependency:

Container Resource Scheduling

The Resource Scheduling is scoped in a container. Resource Scheduling between containers has some limitations. Here is an example:

there is a conflict on scheduling between the tasks at the line 5 and 6.