Project → Task → Sub-task:
Project
A container for larger objectives inside a domain.
Task
A standard executable work item under a project.
Sub-task
A granular step under a task, keyed as
DOMAIN-123.1.OPS-42 or OPS-42.1 for a sub-task.
Creating a work item
Via CLI
Via API
POST /browse with a JSON body:
Listing work items
Getting a work item
GET /browse/:key.
Updating a work item
The equivalent API call is
PATCH /browse/:key.
Status changes must respect valid workflow transitions. Use
oi work-item transitions ABC-123 to see which statuses are reachable from the current state.Scheduling a work item
You can schedule work to a specific date or a timed block, or clear a schedule to move it back to the backlog.Managing comments
Comments let you leave notes and collaborate on a work item. You can control visibility to keep some notes internal.--visibility flag accepts internal (default) or external. External comments are visible in email conversation threads.
Managing attachments
You can attach local files or link external URLs to a work item.Managing dependencies
Track relationships between work items using dependencies.POST /browse/:key/dependencies, GET /browse/:key/dependencies, and DELETE /browse/:key/dependencies/:dependencyId.
Managing categories
Categories are domain-scoped labels for organizing work items.POST /browse/:key/categories and DELETE /browse/:key/categories/:categoryId.
Viewing hierarchy
See the full parent-child tree for a work item:GET /browse/:key/hierarchy.
Audit history
Every mutation to a work item is recorded. To inspect the change history:Deleting a work item
DELETE /browse/:key. Deletion is permission-checked and key-targeted.