Reference & Data Model
Dependency (project_item_dependency)
A dependency links the start or end of one planning object to the start or end of another; it controls the order the optimizer respects.
Purpose
Section titled “Purpose”Dependencies link tasks, milestones and gates. The source (source_id) is the predecessor, the target (target_id) the successor. (Data type: planning data, work plan)
Where in the app
Section titled “Where in the app”Task/Milestone/Gate › context menu or side panel › „Abhängigkeiten“ (Dependencies) › „Neue Abhängigkeit“ (New dependency; search object, choose type); in the Gantt by dragging from connection point to connection point, remove with Del. See Guides › Gantt.
Fields
Section titled “Fields”| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Type | type |
Selection | yes | Linked anchors, see table | Default „Ende zu Start“ (End to start) |
| Depends on | source_id |
Reference (Task/Milestone/Gate) | yes | Predecessor | |
| Target | target_id |
Reference (Task/Milestone/Gate) | yes | Successor; the object from which the dialog was opened |
| Value | Label | Meaning |
|---|---|---|
end_start |
Ende zu Start | Predecessor must end before successor starts (FS, default) |
start_start |
Start zu Start | Predecessor must start before successor starts (SS) |
end_end |
Ende zu Ende | Predecessor must end before successor ends (FF) |
start_end |
Start zu Ende | Predecessor must start before successor ends (SF, rare) |
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Predecessor / successor (Task, Milestone, Gate) | reference without foreign key | yes | – | dependency is deleted along as soon as one endpoint is deleted |
Rules & automation
Section titled “Rules & automation”- No automatic shifting: if a predecessor is moved in the Gantt, the successor does not move with it; a dependency does not shift anything by itself from Execution on either. It is a constraint for the optimizer, which respects all four types and reconciles the plan on the next computation.
- The Gantt shows dependencies as arrows; there is no critical path.
- An object cannot depend on itself (locked in the dialog).