# Asana Cross-Project Dependency Tracker

> Track dependencies across Asana projects. Find blocked chains, overdue dependencies, and at-risk deliverables automatically.

Source: https://cotera.co/solutions/ops/asana-cross-project-dependency-tracker

---

- **Team:** Operations
- **Tools:** Asana
- **Difficulty:** advanced
- **Setup time:** 15 min
- **Time saved:** 2-3 hrs/week

## How it works
1. **Scan Projects** — Pulls tasks from multiple projects and maps out which tasks depend on each other across project boundaries
2. **Trace Chains** — Follows dependency chains across projects to find root blockers causing cascading delays
3. **Flag Risks** — Identifies overdue dependencies and projects where a large percentage of work is blocked externally
4. **Post Context** — Adds comments on blocked tasks explaining what is holding them up and who owns the blocker

## Example requests
- Check for cross-project dependencies between the API Backend and Mobile App projects
- Find all blocked chains across our active projects and post comments on the root blockers
- Which projects are at risk because of overdue dependencies in other projects?

## Prompt

```markdown
## Task

Use @Asana/List Projects to scan multiple projects, @Asana/List Tasks and @Asana/Get Task to identify tasks with cross-project dependencies. Find blocked chains, tasks where dependencies are overdue, and projects at risk. Use @Asana/Add Comment to post context on blocked tasks.

## Input

The user provides:
1. Their Asana workspace or team name
2. The projects to scan (or "all active projects")
3. Specific areas of concern (optional, e.g., "focus on the API and Frontend projects")

**Example:** "Check for cross-project dependencies between the API Backend and Mobile App projects"

## Context

### Project Scanning

1. Use @Asana/List Projects to find all active projects in the workspace
2. Filter to the projects the user specified (or scan all)
3. Use @Asana/List Tasks for each project to build a complete task inventory

### Dependency Discovery

1. Use @Asana/Get Task on tasks that have dependencies to pull full dependency details
2. Map out which tasks depend on tasks in other projects
3. Build a dependency graph showing cross-project relationships
4. Identify tasks that are blocking work in a different project

### Blocked Chain Analysis

For each cross-project dependency, check:

**Overdue Dependencies:**
- The blocking task is past its due date, causing downstream delays
- Calculate how many days overdue and estimate the ripple effect

**Blocked Chains:**
- Task A (Project X) blocks Task B (Project Y) which blocks Task C (Project Z)
- Identify the root blocker in multi-step chains
- Flag the longest blocked chains first

**At-Risk Deliverables:**
- Tasks with dependencies that are incomplete and due soon
- Projects where a significant percentage of remaining work is blocked by another project

### Posting Context

1. Use @Asana/Add Comment on blocked tasks to explain what's holding them up
2. Include: "This task is blocked by [Task Name] in [Project Name], which is [X days overdue / in progress / not started]"
3. Tag the dependency so the blocker's owner has visibility
4. Add comments to the blocking task noting which downstream tasks are waiting

### Safety Guidelines

- Only add comments, never change task assignments or due dates without confirmation
- Flag ambiguous dependencies for human review
- Report on dependencies you can't fully resolve (e.g., external blockers)

## Output

**Cross-Project Dependency Report:**

**Projects Scanned:** [count]
**Cross-Project Dependencies Found:** [count]

**Blocked Chains:**
1. [Root blocker task] (Project A) → [Blocked task] (Project B) → [Downstream task] (Project C)
   - Root blocker status: [status], due: [date], assignee: [person]
   - Days blocked: [X]

**Overdue Dependencies:**
- [Blocking task] in [Project] is [X] days overdue
  - Blocking [count] tasks across [count] projects
  - Impact: [description of downstream effect]

**At-Risk Deliverables:**
- [Project Name]: [X]% of remaining tasks blocked by other projects
- Key risk: [task name] depends on [overdue/stalled dependency]

**Comments Posted:** [count] tasks updated with dependency context

**Recommended Actions:**
1. [Highest priority action to unblock the most work]
2. [Second priority action]
3. [Additional recommendations]
```

## Related reading
- [Asana API: We Built a Custom Integration. Then We Stopped Maintaining It.](https://cotera.co/articles/asana-workflow-examples.md)