Skip to main content
As your workspace grows, labels and dependencies help you categorize and prioritize work.

Quick Start

1

Create Labels

Create color-coded tags to categorize issues across your workspace.
# Create "bug" label (red)
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/labels \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"bug","color":"#FF0000"}' \
  --max-time 10

# Create "feature" label (blue)
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/labels \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"feature","color":"#0066FF"}' \
  --max-time 10
2

Link Dependencies

Connect related issues to show workflow relationships.
# Issue A blocks Issue B
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$ISSUE_A/dependencies/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"depends_on_issue_id":"ISSUE_B_ID","type":"blocks"}' \
  --max-time 10

How Labels Work

Labels are color-coded tags you attach to issues for easy categorization and filtering.

Label Management

ActionDescription
CreateDefine workspace-wide labels with colors
TagAttach labels to issues
FilterFind issues by label
RemoveUntag labels from issues

Tag an Issue

curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$ISSUE_ID/labels/$LABEL_ID \
  -H "Authorization: Bearer $TOKEN" \
  --max-time 10

List Issue Labels

curl -s http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$ISSUE_ID/labels \
  -H "Authorization: Bearer $TOKEN" \
  --max-time 10

How Dependencies Work

Dependencies link issues to show relationships and execution order.

Dependency Types

TypeDescriptionUse Case
blocksMust finish before dependent can startSequential work
relatedConnected but not blockingContext sharing
duplicatesSame work, different issuesIssue cleanup

View Dependencies

curl -s http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$ISSUE_A/dependencies/ \
  -H "Authorization: Bearer $TOKEN" \
  --max-time 10

Putting It Together

Organize a complete workflow using labels and dependencies.

Example: Backend Feature Pipeline

# Create backend label
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/labels \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"backend","color":"#6366F1"}' \
  --max-time 10

# Create three issues
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title":"Setup Database"}' \
  --max-time 10

curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title":"Build API"}' \
  --max-time 10

curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title":"Write Tests"}' \
  --max-time 10

# Tag all with backend label
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$DB_ISSUE_ID/labels/$BACKEND_LABEL_ID \
  -H "Authorization: Bearer $TOKEN" \
  --max-time 10

# Create dependency chain: DB blocks API blocks Tests
curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$DB_ISSUE_ID/dependencies/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"depends_on_issue_id":"API_ISSUE_ID","type":"blocks"}' \
  --max-time 10

curl -s -X POST http://localhost:8000/api/v1/workspaces/$WS_ID/issues/$API_ISSUE_ID/dependencies/ \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"depends_on_issue_id":"TESTS_ISSUE_ID","type":"blocks"}' \
  --max-time 10

Best Practices

Create standard labels like “bug”, “feature”, “urgent” that team members recognize. Avoid duplicate labels with similar meanings.
Use red for urgent issues, blue for features, green for improvements. Consistent colors help visual scanning.
Map blocking relationships before starting work. This prevents bottlenecks and clarifies execution order.
Check if blocking issues are resolved and update dependency status. Remove outdated links to keep the graph clean.

Platform Issues

Create and manage issues in your workspace

Issue IDs

Understanding issue identification and references