MyStatusFlow Docs

Task Chaining

Quickly create sequential task chains using the Link A → B feature to set up predecessor relationships.

What is task chaining?

  • definition: Creating sequential predecessor relationships between multiple tasks in one action.
  • feature: "Link A → B" button in the toolbar creates chains automatically.
  • result: Each task after the first gets a predecessor pointing to the previous task.
  • relationship type: Creates Finish-to-Start (FS) relationships by default.

How to chain tasks

  1. Select tasks: Click checkboxes to select 2 or more tasks in order.

    • First selected task = A (predecessor)
    • Second selected task = B (successor)
    • Third selected task = C (successor to B)
    • And so on...
  2. Click Link A → B: Button appears in toolbar when 2+ tasks are selected.

  3. Review results: Predecessors are set automatically:

    • Task B gets predecessor: A
    • Task C gets predecessor: B
    • Task D gets predecessor: C

Selection order matters

  • first clicked: Becomes the first task in the chain (has no predecessor).
  • subsequent clicks: Each becomes a successor to the previous.
  • display order fallback: If selection order is unclear, uses visible row order.

Example workflow

Before:

Task 1: "Design"
Task 2: "Development"
Task 3: "Testing"
Task 4: "Deployment"

Select: Task 1, Task 2, Task 3, Task 4 (in order)

Click: Link A → B

After:

Task 1: "Design" (no predecessor)
Task 2: "Development" (predecessor: 1)
Task 3: "Testing" (predecessor: 2)
Task 4: "Deployment" (predecessor: 3)

How chaining works

Sequential linking

  • chain creation: Each task after the first gets predecessor set to immediately previous task.
  • preserves existing: Existing predecessors are preserved; new links are added.
  • deduplication: No duplicate predecessors created.

Relationship type

  • default: Finish-to-Start (FS) relationships are created.
  • format: Predecessors are set as simple IDs (e.g., 1, 2, 3), which default to FS.
  • no lag: Zero lag by default (can add lag manually later).

Chain structure

Created chain:

Task 1 → Task 2 → Task 3 → Task 4

Scheduling result:

  • Task 1 starts first (no predecessor).
  • Task 2 starts after Task 1 finishes.
  • Task 3 starts after Task 2 finishes.
  • Task 4 starts after Task 3 finishes.

Partial chaining

Adding to existing chain

  • preserves existing: If tasks already have predecessors, new links are added.
  • ordered list: New predecessors are added first, then existing ones.

Example:

  • Task 3 already has predecessor: 5
  • Link Task 2 → Task 3
  • Result: Task 3 predecessors = 2, 5

Chaining subsets

  • select any tasks: You don't need to select all tasks in a project.
  • chain just what you need: Select only the tasks you want to chain together.

Example:

  • Select: Task 3, Task 5, Task 8
  • Result: Task 5 → Task 3, Task 8 → Task 5

Scheduling impact

Automatic date calculation

  • cascading dates: When you chain tasks, dates are automatically recalculated.
  • business day aware: All date math respects business days and working hours.
  • sequential flow: Tasks start one after another based on predecessor finishes.

Example timeline

Task 1:

  • Duration: 5 days
  • Start: Monday 8am
  • Finish: Friday 5pm

Task 2 (after chaining):

  • Predecessor: 1FS
  • Start: Monday 8am (next business day after Task 1 finishes)
  • Finish: Friday 5pm (Start + Duration)

Task 3 (after chaining):

  • Predecessor: 2FS
  • Start: Monday 8am (next business day after Task 2 finishes)
  • Finish: Friday 5pm (Start + Duration)

Unlinking tasks

Remove from chain

  • clear predecessors: Delete predecessor IDs from the Predecessors cell.
  • automatic recalculation: Dates recalculate immediately when predecessors are removed.
  • preserve other tasks: Other tasks in the chain remain linked.

Example:

  • Task 3 has predecessor: 2
  • Delete 2 from Task 3's Predecessors cell.
  • Task 3 is unlinked; can start independently.
  • Task 2 → Task 4 chain remains intact.

Validation

Valid chains

  • no cycles: System prevents circular dependencies.
  • no self-links: Tasks cannot depend on themselves.
  • no ancestor links: Tasks cannot depend on their parents.

Invalid configurations

  • milestones: Milestones cannot have predecessors (cannot be successors).
  • summary tasks: Parent tasks (groups) cannot have predecessors.
  • cycles: Circular chains are detected and blocked.

Examples

Example 1: Simple 3-task chain

Before:

  • Task 1: "Requirements"
  • Task 2: "Design"
  • Task 3: "Build"

Action: Select Task 1, Task 2, Task 3 → Link A → B

After:

  • Task 1: "Requirements" (predecessors: none)
  • Task 2: "Design" (predecessors: 1)
  • Task 3: "Build" (predecessors: 2)

Schedule:

  • Task 1 starts first.
  • Task 2 starts after Task 1 finishes.
  • Task 3 starts after Task 2 finishes.

Example 2: Adding to existing chain

Before:

  • Task 1 → Task 2 (already linked)
  • Task 3: "New Task" (no predecessor)

Action: Select Task 2, Task 3 → Link A → B

After:

  • Task 1 → Task 2 → Task 3 (extended chain)

Example 3: Partial chain

Before:

  • Task 1: "Planning"
  • Task 2: "Design"
  • Task 3: "Development"
  • Task 4: "Testing" (already has predecessor: 1)

Action: Select Task 2, Task 3 → Link A → B

After:

  • Task 1: "Planning"
  • Task 2: "Design"
  • Task 3: "Development" (predecessors: 2)
  • Task 4: "Testing" (predecessors: 1 - preserved)

Tips

  • Plan your chain: Think about the order before selecting tasks.
  • Select in order: Click tasks in the order you want them to execute.
  • Review dates: Check that dates cascade correctly after chaining.
  • Use for sequential work: Chaining is perfect for waterfall-style workflows.
  • Combine with other relationships: You can manually add SS, FF, SF relationships after chaining.

FAQ

Can I chain more than 2 tasks at once?

Yes. Select as many tasks as you want (2+), then click Link A → B. They'll be chained sequentially.

What if I select tasks in the wrong order?

The first task you click becomes the start of the chain. If you need a different order, deselect and re-select in the correct order.

Can I add lag time to chained tasks?

Yes. After chaining, edit the Predecessors cell to add lag: 1FS+2 for a 2-day delay.

What happens if I chain tasks that already have predecessors?

Existing predecessors are preserved. New chain links are added to the list (new links first, then existing).

Can I unchain just one task?

Yes. Delete its predecessor from the Predecessors cell. Other tasks in the chain remain linked.

What if I want Start-to-Start instead of Finish-to-Start?

Link A → B creates FS relationships. After chaining, manually edit Predecessors to change to SS (e.g., 1SS).

Can I chain a parent task (group)?

No. Parent tasks cannot have predecessors. Chain the children instead.


Last updated: 2025‑01‑15