Auto Scheduling Settings: Strict vs. Not Strict Scheduling
You can manage exactly how you want the dependencies to perform by choosing either 'Off', 'On', or 'Strict' or dependency relationships for a project on the 'Auto scheduling' settings page under the 'More' menu.
Additionally, the default auto-scheduling setting for new projects can be set on the Workspace Settings page by Admins. Note: Project Template auto-scheduling settings will override the default for new projects.
'Off': Duration and date changes to dependency and predecessor actions will not adjust other actions in the project.
'On': This will favor the dependent action's start date rather than the dependency link itself, meaning that the preceding action can move forward in time without affecting the dependent action. Only once the predecessor has passed the start date of the dependent action, will the dependent action move forward.
Additionally, if a predecessor action is completed in a shorter duration than planned, the dependent actions will not move forward automatically to account for the shorter duration adjustment.
'Strict': Strict scheduling (or 'ASAP' scheduling) means that all actions move together, no matter which direction they are moving. This is also where you can set strict lag or gap time. If a predecessor action is completed in a shorter duration than planned, the dependent actions will move forward automatically to account for the shorter duration adjustment.
Create the dependencies as normal. To create lag time, either click on the dependency link itself or write the advanced predecessor in the 'Predecessor' column. Now when one action moves forward or backward in time, they will all move together.
Pro-tip: when updating auto-scheduling settings, an update to the project is needed in order for the updated setting to apply. Slightly drag the action card's bar to trigger the update.
Additionally, the predecessor column in Gantt is also where you can write advanced dependency functions (FS, FF, SS, SF + "Xd"). Use the formulate to add days of "lag" to the previous dependency. Like, "1.1FS+2d".
When it comes to dependencies you can use in your Gantt projects, there are 4 types of those:
Finish-to-start (FS) - You cannot start action B before action A is completed
This type of dependency can be applied when you need one task to be finished before the next one can be started.Finish-to-finish (FF) - You cannot complete action B before action A is done
If you don't want to finish an action before the preceding one is completed, this type of dependency will be the one to go for.
Start-to-start (SS) - You cannot start Action B before action A starts
Sometimes you might need to have one action start before letting the following one kick off. This type of dependency will allow you to do that.
Start-to-finish (SF) - You cannot complete action A before action B starts
With this type of dependency, the preceding action cannot be marked as completed up until the following action starts.
You may also set the default Gantt auto scheduling for the workspace, in the Workspace Settings page.
Using Auto Scheduling in Other Views
In response to our users’ feedback, we have implemented the Auto Scheduling feature in additional views.
Previously, the Auto Scheduling feature was limited to moving the predecessor or successor action cards in the Gantt View. However, users now can anticipate this functionality to be available in all of their views.
To utilize this feature, ensure that the project’s auto scheduling setting is set to either “On” or “Strict” within the project’s settings.
Once the setting is set to “On/Strict,” you will be able to modify the due date of an action card, and the subsequent dependent action card will automatically adjust accordingly.
Gantt View
The Gantt View is where the majority of our users utilize the Auto Scheduling feature. You can easily observe the modifications you make by moving an action card forward or backward. (The following example illustrates the Strict auto scheduling setting.)
Table View
In the Table View, users can modify the due date of an action card to shift the dates. Changing the start date will revert it to the previous action card’s start date, as the previous action card determines the start date. (The following example illustrates the Strict auto scheduling setting.)
List View
In the List View, users can modify the due date of an action card to shift the dates. Changing the start date will revert it to the previous action card’s start date, as the previous action card determines the start date. (The following example illustrates the Strict auto scheduling setting.)
Kanban View
In the Kanban View, you will need to open the action card modal and update the due date to use the auto scheduling feature. (The following example illustrates the Strict auto scheduling setting.)
Calendar View
In the Calendar View, similar to the Kanban View, users will need to open the action card modal and update the due date. (The following example illustrates the Strict auto scheduling setting.)
