Skip to main content
Work items are the core unit of work in OpenIndex. Every piece of work — whether a large initiative, an individual task, or a granular step — lives as a work item with a consistent structure and key. OpenIndex has three kinds of work items that follow the hierarchy 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.
Work-item keys are domain-scoped and sequential — for example, OPS-42 or OPS-42.1 for a sub-task.

Creating a work item

Via CLI

Additional create flags:

Via API

POST /browse with a JSON body:

Listing work items

Filter the list with any combination of these flags:

Getting a work item

This returns the full work item record, including its current status, priority, workflow assignment, schedule, and metadata. The equivalent API call is GET /browse/:key.

Updating a work item

Available update flags: 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.
Scheduled work items appear alongside external calendar events in the calendar view.

Managing comments

Comments let you leave notes and collaborate on a work item. You can control visibility to keep some notes internal.
The --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.
The API equivalents are 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.
The API equivalents are POST /browse/:key/categories and DELETE /browse/:key/categories/:categoryId.

Viewing hierarchy

See the full parent-child tree for a work item:
The API equivalent is GET /browse/:key/hierarchy.

Audit history

Every mutation to a work item is recorded. To inspect the change history:
You can also export the audit log:

Deleting a work item

The API equivalent is DELETE /browse/:key. Deletion is permission-checked and key-targeted.
Deleting a work item is permanent. There is no undo.