Skip to main content

Syntax

tracer dep add <issue_id> <depends_on_id> [OPTIONS]

Parameters

issue_id
string
required
The issue ID that depends on another issue
depends_on_id
string
required
The issue ID that is depended on

Options

--type
string
default:"blocks"
Dependency type. Available values:
  • blocks - Issue is blocked by the dependency
  • related - Issues are related but don’t block
  • parent-child - Parent-child relationship (for epics)
  • discovered-from - Issue was discovered while working on another
Short flag: -t
--json
boolean
Output result in JSON format

Examples

# Add a blocking dependency
tracer dep add bd-2 bd-1

Output

Human-Readable Format

✓ Added dependency: bd-2 --blocks--> bd-1

JSON Format

{
  "issue_id": "bd-2",
  "depends_on_id": "bd-1",
  "type": "blocks",
  "created_at": "2025-03-04T10:30:00Z",
  "created_by": "[email protected]"
}
Both issues must exist before creating a dependency. The command will fail if either issue ID is not found.
Use tracer dep tree <issue_id> to visualize the complete dependency graph after adding dependencies.

Build docs developers (and LLMs) love