Primary Question

How should a project be set up so that a DPM project task with multiple predecessors—potentially across multiple phases—only moves to “To Do” after all predecessor tasks are completed (true AND logic)?

Context

We are implementing a dependency-driven process where:

• Tasks auto-promote to “To Do” only when work is truly ready

• Users rely on notifications instead of monitoring schedules

• Parallel work must not trigger downstream tasks prematurely

What We’re Seeing

When a task has multiple predecessors:

• It moves to “To Do” as soon as any one predecessor is complete

• This behaves like OR logic, not AND logic

Example:

• Task A + Task B (parallel) (these tasks could be in separate project phases, so can't always put them under a summary/parent task)

• Task C should start after A AND B

• Today: completing A alone moves C to “To Do” (currently, I've tried using finish to start dependencies from A to C and from B to C.)

Impact

• Users are notified too early

• Work starts without all required inputs

• Manual intervention is needed to delay tasks

This breaks the intended dependency-driven workflow.

What We Need

• Confirmation if this is behaving as designed 

• If it's supported, guidance on how to set up true AND dependency logic

• If it's not supported, the recommended method for setting up a project

Goal

Ensure tasks only become actionable when all required upstream work is complete, so we can rely on auto-promotion and notifications to drive task execution.