Skip to main content

​
Understanding tickets

Tickets are the core work items in Toots. Each ticket represents a discrete piece of work with all the context your team or coding agent needs to complete it.

​
Ticket types

Toots supports five ticket types:
  • Story: User-facing features or functionality
  • Task: Individual work items that contribute to a larger goal
  • Epic: Large bodies of work that encompass multiple stories or tasks
  • Milestone: Key checkpoints or deliverables in your project timeline
  • Deliverable: Concrete outputs or artifacts that must be produced

​
Ticket properties

Each ticket includes:
  • Title: Clear, action-oriented summary
  • Description: What needs to be done and why it matters
  • Priority: P0 (critical), P1 (high), P2 (medium), or P3 (low)
  • Status: To Do, In Progress, or Done
  • Estimated effort: XS, S, M, L, or XL
  • Acceptance criteria: Conditions that must be met for the ticket to be complete
  • Dependencies: Other tickets that must be completed first
  • Labels: Tags for categorization and filtering

​
Viewing ticket details

1

Open the ticket sheet

Click any ticket card on the Kanban board to open a slide-out detail sheet.
2

Review ticket information

The detail sheet displays all ticket properties, including the full description, acceptance criteria, dependencies, and labels.

​
Editing tickets

You can edit tickets manually through the UI or ask the AI to make changes via the project chat.

​
Manual editing

1

Open the ticket

Click the ticket card to open the detail sheet.
2

Edit fields

Click any editable field to modify it:
  • Update the title or description
  • Change the type, priority, or estimated effort
  • Add or remove acceptance criteria
  • Modify dependencies or labels
3

Save changes

Changes are saved automatically when you update a field.

​
AI-assisted editing

You can also ask the AI to modify tickets through the project chat. See Using AI chat for details.

​
Updating ticket status

Tickets move through three status columns on the Kanban board:
1

Drag and drop

Click and drag a ticket card to move it between columns:
  • To Do: Work that hasn’t started
  • In Progress: Active work items
  • Done: Completed tickets
2

Status persists

Status changes are saved automatically and persist across sessions.
You can also update status by opening the ticket detail sheet and changing the status field directly.

​
Reordering tickets

Tickets within each column can be reordered by dragging and dropping:
  1. Click and hold a ticket card
  2. Drag it to the desired position within its column
  3. Release to set the new order
The sort order is preserved and determines how tickets appear on the board.

​
Deleting tickets

1

Open the ticket

Click the ticket card to open the detail sheet.
2

Click delete

Click the delete button or icon in the detail sheet.
3

Confirm deletion

Confirm that you want to delete the ticket.
Deleting a ticket is permanent and cannot be undone. If other tickets depend on this ticket, you may need to update their dependencies.

​
Deleting via AI chat

You can also ask the AI to remove tickets through the project chat: 
Remove the onboarding ticket
The AI will use the listTickets tool to find the ticket by name, then call removeTickets to delete it.

​
Ticket dependencies

When a ticket depends on others, the dependencies are listed in the ticket detail. This helps you understand the order in which work should be completed. To update dependencies:
  1. Open the ticket detail sheet
  2. Edit the dependencies field
  3. Enter the IDs of tickets this one depends on
Dependencies are stored as an array of ticket IDs (e.g., ["ticket-1", "ticket-3"]).

​
Next steps

Using AI chat

Let the AI help you modify, add, or remove tickets

Exporting tickets

Send your tickets to Jira or Linear (coming soon)

Build docs developers (and LLMs) love

Get started for freeTalk to us