Ticket Dependencies

​

Overview

​

How Dependencies Work

• A ticket cannot execute until its blocker reaches DONE
• The planner automatically blocks tickets with incomplete dependencies
• When a dependency completes, blocked tickets are auto-unblocked

​

Setting Dependencies

​

Via the UI

​

Via the API

curl -X PATCH http://localhost:8000/tickets/{id} \
  -H "Content-Type: application/json" \
  -d '{"blocked_by_ticket_id": "other-ticket-id"}'

​

Execution Order

1. Build a dependency graph from all tickets
2. Find tickets with no dependencies (ready to execute)
3. Execute in priority order
4. When a ticket completes, check if any blocked tickets are now unblocked

​

Cycle Detection

​

Example

Ticket A: "Set up database schema"
    ↓
Ticket B: "Add API endpoints" (blocked by A)
    ↓
Ticket C: "Add frontend pages" (blocked by B)

​

Best Practices

• Keep dependency chains short (2-3 levels max)
• Use dependencies for true data/API dependencies, not just priority ordering
• Let the planner handle dependency management when using autopilot