Skip to content

How auto-scroll works

When a task’s date changes or a new dependency is created, SmartPM pushes dependent tasks forward while preserving their durations. The rule applies only to forward-moving tasks; it does not touch appropriate dates.

  • All users

How does automatic shifting work?

When a task's date changes or a new dependency is created, SmartPM shifts dependent tasks forward while preserving their durations. Who can do this: All users. A notification appears at the bottom of the screen: "N tasks shifted forward due to dependency," and the shift is logged in the history of floating tasks. The rule only applies forward; appropriate dates remain untouched.

Rule

  • For each task, the earliest possible start date allowed by its predecessors is calculated.
  • If a task starts before this date, it is shifted to that date while preserving its working day duration.
  • If the task already starts later, the date remains unchanged.
  • Weekends are not counted as working days.

Tracking the shift

  1. Drag the predecessor task's end date forward via the task panel or Gantt chart.

  2. Read the notification at the bottom of the screen: "N tasks shifted forward due to dependency."

  3. Check the new positions of floating successors on the Gantt chart.

Example

“Homepage design” starts on Monday and ends on Friday, and “Design approval” is linked to it with starts when finished. If you extend the design's end to the following Tuesday, the approval moves to Wednesday; the approval's successors shift in turn.

Result A notification appears at the bottom of the screen: "N tasks were shifted forward due to dependencies." The shifting history of the affected tasks is recorded.
Tip Shortening a predecessor or removing a dependency does not pull successors back. To bring a successor forward, change its date manually; this is accepted if constraints allow.

Related pages