Skip to main content

Syntax

tracer dep tree <id> [OPTIONS]

Parameters

id
string
required
Root issue ID to display the dependency tree for

Options

--max-depth
integer
default:"50"
Maximum depth to traverse in the dependency tree
--json
boolean
Output result in JSON format

Examples

# Show dependency tree for bd-1
tracer dep tree bd-1

Output

Human-Readable Format

Dependency tree for bd-1:

bd-1 Implement user authentication [P1, open]
  └─ bd-2 Design auth schema [P1, in_progress]
    └─ bd-5 Research OAuth providers [P2, open]
  └─ bd-3 Create login endpoint [P1, open]
  └─ bd-4 Add session management [P1, blocked]
    └─ bd-2 Design auth schema [P1, in_progress] [...]
The [...] marker indicates that a branch has been truncated to avoid showing circular dependencies or exceeding max depth.

JSON Format

[
  {
    "id": "bd-1",
    "title": "Implement user authentication",
    "status": "open",
    "priority": 1,
    "issue_type": "epic",
    "assignee": "",
    "created_at": "2025-03-04T10:00:00Z",
    "updated_at": "2025-03-04T10:00:00Z",
    "depth": 0,
    "truncated": false
  },
  {
    "id": "bd-2",
    "title": "Design auth schema",
    "status": "in_progress",
    "priority": 1,
    "issue_type": "task",
    "assignee": "[email protected]",
    "created_at": "2025-03-04T10:05:00Z",
    "updated_at": "2025-03-04T11:00:00Z",
    "depth": 1,
    "truncated": false
  },
  {
    "id": "bd-5",
    "title": "Research OAuth providers",
    "status": "open",
    "priority": 2,
    "issue_type": "task",
    "assignee": "",
    "created_at": "2025-03-04T10:15:00Z",
    "updated_at": "2025-03-04T10:15:00Z",
    "depth": 2,
    "truncated": false
  }
]
The tree shows all transitive dependencies, making it easy to understand the full scope of work required to complete an issue.

Build docs developers (and LLMs) love