DocumentaciónHelp

Dependencies between tasks

Link tasks and milestones so one starts or finishes based on another, with lag or lead in working days.

On this page

A dependency says that one row (the successor) can't start or finish until another one (the predecessor) starts or finishes. With dependencies, Elion ITSM automatically moves the tasks that come after when something is delayed or moves earlier.

Before you start

  • You must be a Lead or Member of the desk.

  • The project needs at least two tasks or milestones.

  • Dependencies go between tasks and milestones. You can't link phases or tasks that have subtasks: link the tasks inside them.

Dependency types

Type

Meaning

Example

FS · Finish → start

The successor starts the working day after the predecessor finishes

Build after designing

SS · Start → start

The successor starts when the predecessor starts

Document while building

FF · Finish → finish

The successor finishes when the predecessor finishes

Tests that close along with the build

SF · Start → finish

The successor finishes when the predecessor starts

A shift that ends when the next one starts

The Lag (working days) adds days to that rule. A negative lag is a lead: for example, FS with −2 makes the successor start 2 working days before the predecessor finishes. The form accepts half days, but the calculation rounds the lag to the nearest whole day, because the plan is counted by day.

Create a dependency from the form

  1. In the Gantt or the List, press Dependency.

  2. In the New dependency form, choose:

    • Predecessor: the row it depends on.

    • Successor: the row that waits.

    • Type: FS, SS, FF or SF.

    • Lag (working days): 0 if there is no wait. Negative = lead.

  3. Press Add.

In the List, the link icon button on each row (Add predecessor to that row) opens the form with the successor already chosen. In the Gantt, if a bar is selected, Dependency suggests it as the predecessor.

Create a dependency by dragging in the Gantt

  1. Hover over a bar: two dots appear at its ends.

  2. Drag from the dot at the matching end (the finish or the start of the predecessor).

  3. Drop on the left half of another bar (its start) or on the right half (its finish).

The type comes from the ends you joined: finish to start is Finish → start, start to start is Start → start, and so on. Drawn dependencies have no lag; to add one, create the same dependency from the form with the lag you need.

If you add a dependency between two rows that were already linked, it isn't duplicated: its type and lag are replaced.

See the dependencies

  • In the Gantt, each dependency is an arrow; it's red if it joins two rows on the critical path. Hover over the arrow to see the type and the lag.

  • In the List, the Predecessors column shows each one as number type lag, for example OBRA-3 FS+2.

Remove a dependency

  1. In the Gantt, click the arrow (or reach it with Tab and press Enter).

  2. In the Remove dependency dialog, check which rows are the predecessor and the successor, and press Remove.

Rules that are validated

  • A row cannot depend on itself. The form won't save if the predecessor and the successor are the same.

  • Cycles aren't allowed. If A depends on B and B depends on A (directly or indirectly), the message says the dependency forms a cycle and shows the rows involved.

  • A project allows up to 5,000 dependencies.

What happens next

Elion ITSM immediately recalculates the successor and the ones after it, the phase dates and the Critical path. Tasks that have a Fixed Date constraints or that already have an Actual start don't move even if a predecessor changes.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

↑↓ to navigate · Enter to open · Esc to close