Implement Proper Ticket Blocking/Dependency System

Tinker

Home Epics Implement Proper Ticket Blocking/Dependency SystemEdit

Cancel

Title *

Project *

Description

## Problem

Tickets have `parent_id` for hierarchical relationships (subtasks), but there's no explicit "blocked by" or "depends on" relationship. Agents cannot:
- See which tickets are blocking their work
- Mark tickets as waiting for other tickets
- Automatically track dependency chains

## Current State

- `parent_id` exists but only shows subtask hierarchy
- `working_memory` can store `depends_on_ticket` but agents don't check it
- No visual indicator in UI for blocked tickets
- No automatic dependency resolution

## Solution

Implement a proper ticket blocking/dependency system:

1. **Database schema** - Add `blocked_by_id` or `dependencies` array
2. **Agent awareness** - Agents check blocking status before starting work
3. **UI indicators** - Show blocked tickets visually
4. **Auto-unblock** - When blocking ticket completes, unblock dependent tickets

## Implementation Ideas

### Option A: Single Blocker
```ruby
add_column :tickets, :blocked_by_id, :integer, foreign_key: { to_table: :tickets }
```

### Option B: Multiple Dependencies
```ruby
add_column :tickets, :blocking_ticket_ids, :integer, array: true
```

### Option C: Join Table (Most Flexible)
```ruby
create_table :ticket_dependencies do |t|
  t.references :ticket, null: false
  t.references :blocks, null: false, foreign_key: { to_table: :tickets }
  t.timestamps
end
```

## Agent Behavior

Agents should:
- Check if ticket has blockers before starting work
- Comment "waiting for ticket #X" if blocked
- Not start work on blocked tickets
- Notify dependent tickets when completing work

## Acceptance Criteria

1. Database schema supports ticket dependencies
2. API can read/write blocking relationships
3. Agents check blockers before working
4. UI shows blocked status visually
5. Completing a ticket auto-unblocks dependents (optional)