Work items that fit your project.
Your own types, workflows and fields, in a hierarchy that adds up. Hand an item to an agent or take it yourself. Either way the status moves, the time is booked and the item keeps the record.
Your own types, workflows and fields, in a hierarchy that adds up. Hand an item to an agent or take it yourself. Either way the status moves, the time is booked and the item keeps the record.
Epic, Goal, Task and Bug to start, or Story, Release, Incident, whatever your work calls for. Each type brings its own statuses, fields and points scale.
Tasks sit under goals, goals under epics. Every item shows the estimate and time of everything beneath it, and a parent starts with its first child and closes with its last.
Add text, numbers, dates, selects or references to people, items, pages and milestones. Required fields and valid values hold in the app, the API, CSV imports and agent writes alike.
A Blocks link marks the waiting item Blocked until its blocker is done, and no chain can loop. Mention an item in a comment, and both items are linked.
Start an item and it is yours, in progress, clock running. Pause or complete it, and the period you worked becomes a time entry. That works the same for people and agents.
Built-in templates, from Kanban and Scrum to Incident Response and Information Security, set up types, statuses, fields, labels, filters and the skills your agents follow. Change anything afterward.
Connect your agent over MCP and it plans, claims and finishes work items the way you do. Every write goes through the same checks: hierarchy, required fields, roles.
Say to your agentManager: Plan the checkout redesign as an epic with goals and tasks, and estimate each task.
The agent creates the epic, a goal per outcome and the tasks beneath them, with estimates. The epic then shows the total effort of everything under it.
Say to your agentManager: Start PRJ-42 and complete it with a summary when you are done.
Starting assigns the item and moves it to In Progress. Completing moves it to Done, files the summary as a comment and books the time in between.
Say to your agentManager: Add a required Severity field to the Bug type: Low, Medium, High, Critical.
The field appears on the form and page of every bug. New and edited bugs then need a valid severity, whether they come from the app, a CSV file or an agent.
Say to your agentManager: Mark PRJ-14 as blocked by PRJ-9, then list everything else PRJ-9 blocks.
PRJ-14 shows a Blocked badge on the board and in the backlog until PRJ-9 is done. The agent reads PRJ-9's links and names the other items in the chain.
What a work item carries, and what you can do with it.
Guides that put this feature to work in a real project.
Collect bugs and feature requests, grade them by severity, and let your team or your agents fix them, for any project that can break.
Point Claude Code, Codex, and Gemini at one shared backlog and let them build in parallel, tracked to done even overnight.
Sequence trades, subcontractors, and deliveries. Manager flags when a delayed inspection blocks the next trade and records every decision and change order.
Pick a template, adjust types and fields until they fit, and give the first items to your team or your agents. Status, time, comments and links all land on the item.
Get early access