Issue dependencies express relationships between issues to track blocking, related, and duplicate connections in your project.Documentation Index
Fetch the complete documentation index at: https://docs.praison.ai/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
How It Works
Dependencies are bidirectional - when you create a relationship between Issue A and Issue B, the dependency appears when listing from either issue.Validation Rules
DELETE /workspaces/{ws}/issues/{issue_id}/dependencies/{dep_id} returns 404 Not Found if dep_id does not actually belong to issue_id (neither side of the relationship matches). This prevents deleting unrelated dependencies via URL manipulation.
| Operation | Method | Purpose |
|---|---|---|
| Create | POST | Establish new dependency link |
| List | GET | View all dependencies for an issue |
| Delete | DELETE | Remove specific dependency |
Configuration Options
All endpoints scope resources to the workspace in the URL path. Requesting an
issue_id or dep_id that belongs to a different workspace returns 404 Not Found (never 200 or 403) to avoid leaking the existence of resources across tenants. The depends_on_issue_id is also validated against the URL workspace.API Endpoints
| Method | Endpoint | Description |
|---|---|---|
POST | /api/v1/workspaces/{ws_id}/issues/{issue_id}/dependencies/ | Create dependency |
GET | /api/v1/workspaces/{ws_id}/issues/{issue_id}/dependencies/ | List dependencies |
DELETE | /api/v1/workspaces/{ws_id}/issues/{issue_id}/dependencies/{dep_id} | Delete dependency |
Request Schema
Create Dependency:Dependency Types
| Type | Meaning | Use Case |
|---|---|---|
blocks | This issue blocks the other issue | Issue A must be resolved before Issue B can proceed |
related | Issues are related but not blocking | Similar topics or shared components |
duplicates | This issue is a duplicate of the other | Same problem reported multiple times |
Common Patterns
- Python with httpx
- Bash Scripts
- JavaScript Fetch
Best Practices
Use Clear Dependency Types
Use Clear Dependency Types
Choose the appropriate dependency type:
blocks: Use when one issue must be completed before another can startrelated: Use for issues that share context but don’t block each otherduplicates: Use when multiple issues report the same problem
Avoid Circular Dependencies
Avoid Circular Dependencies
While the API doesn’t prevent circular dependencies, avoid creating chains where Issue A blocks Issue B, and Issue B blocks Issue A. This creates deadlock situations in project planning.
Leverage Bidirectional Lookup
Leverage Bidirectional Lookup
Dependencies appear when querying either issue in the relationship. Use this to discover related work when viewing any issue in your project.
Clean Up Resolved Dependencies
Clean Up Resolved Dependencies
Delete dependencies when issues are resolved to keep the dependency graph clean and relevant for active work.
Dependency Deletion Security
Dependency Deletion Security
The API guards against cross-issue dependency tampering by validating that dependency IDs actually belong to the issue in the URL before allowing deletion.
Testing
Run the dependency service tests to verify functionality:Related
Issue Management
Core issue creation and management
Workspace API
Workspace-level operations and access

