Managing and Locking Job Dependencies

This article explains how job dependencies work in the Gantt Chart and how dependency locking can be used to control job execution and prevent premature updates.

---

📌 Overview

Job dependencies define the execution order between jobs within the same project. By managing dependencies and lock settings, teams can ensure that jobs are completed in the correct sequence and that downstream work does not start before prerequisites are fulfilled.

The Gantt Chart supports:

• Job-to-job dependencies only

• Finish-to-Start (FS) dependency relationships

• Optional dependency locking to restrict job edits

---

📍 Availability & Access Requirements

• Feature Tier: Premium feature

• Access Required:

  • View and Edit Access of Gantt Chart Page Permission

ℹ️ Dependency management is only available on the Gantt Chart page.
Job detail pages display dependency information but cannot modify it.

---

➕ Creating Job Dependencies

Dependencies can be created directly from the Gantt Chart.

How to create a dependency:

1. Open the Gantt Chart.

2. Hover over a job timeline block.

3. Drag the dependency connector to another job within the same project.

4. Release to create the link.

5. Review the dependency connection.

6. Click Save to apply changes.

⚠️ Dependencies will not take effect until the changes are saved.

---

🤖 Auto-Scheduling Behaviour

When dependencies exist, the system can automatically adjust job timelines based on configuration.

Auto-scheduling triggers when:

• A job’s start or end date is adjusted in the Gantt Chart

• A dependency is created or updated

Auto-scheduling stops when:

• A job in the chain is completed

• A job in the chain is cancelled

• The dependency chain exceeds 50 jobs

• No further blocking or blocked-by relationships exist

ℹ️ Editing dates in the Job Detail page does not trigger auto-scheduling.

---

🔒 Locking Job Dependencies

Dependency locking restricts user actions on a job until its prerequisite job is completed.

Purpose of locking:

• Prevents premature job execution

• Ensures work follows the defined sequence

• Protects critical workflow steps

---

🔐 Dependency Lock States

Locking only becomes effective when the job has at least one blocked-by dependency.

---

⚙️ Locking Logic Explained

Locked job behaviour:

• If Job B is blocked by Job A and locked:

  • Job B cannot be edited

  • Job B cannot change status

  • Job B cannot receive comments

• Unlocks automatically when Job A is completed

Unlocked job behaviour:

• Job details remain editable

• Status cannot be changed to a completed status type

• Unlocks automatically once the blocking job is completed

---

🧠 System Safeguards

To prevent scheduling conflicts, the system enforces:

• Dependency chain limit of 50 jobs

• Automatic halt when encountering completed or cancelled jobs

• Warnings when attempting to lock a job without a blocker

Example system message:

Lock Set – Waiting for a Blocker
This job is locked, but no blocking job is linked yet.

---

👁️ Viewing Dependencies in Job Details

Dependency fields are system-generated and view-only.

Visible fields:

• Blocked by

• Blocking

• Dependency Lock

These fields:

• Are visible in Job View

• Are hidden during job creation and editing

• Cannot be manually modified

---

💾 Saving Dependency Changes

All dependency and lock changes remain pending until saved.

• A save prompt appears when changes are detected

• Leaving the page without saving triggers a confirmation

• Unsaved changes will be discarded if not confirmed