Skip to content
Toado Docs

Archive & restore

Archiving moves a ticket off the active board into the archive view, while preserving all its data, comments, and capture context. It is the right action for “I am done with this and do not want it cluttering the board” without committing to deletion.

Archive vs. delete

Toado does not expose a destructive delete in v1. Every ticket-removal action is archive, which is reversible. Permanent deletion is only available through:

The reasoning: tickets carry capture data (network, console, errors) that is occasionally useful months later. Soft archive lets you reclaim board space without losing the audit trail.

Archiving a ticket

From the ticket detail page:

  • Click Archive in the top right action menu, or
  • Press the keyboard shortcut for archive (see Keyboard shortcuts).

From the board:

  • Right-click a card and choose Archive, or
  • Drag the card to the archive zone (visible at the bottom of the board when dragging).

From an AI agent via MCP: archive_ticket(ticket_id). See Tools reference.

What happens on archive

  • The ticket disappears from the board.
  • It remains visible in the project’s Archive view.
  • Search results include it only when the query opts in (e.g. is:archived qualifier or Show archived filter).
  • Comments and attachments are preserved as-is.
  • The column the ticket was in is recorded so restore knows where to put it back.

The archive view

Each project has an Archive page reachable from Project menu › Archive or directly at /projects/<id>/archive. It shows archived tickets sorted by archive date (most recent first), with the same Cards / Table view options as the live board.

Restoring

From the archive view:

  • Open the ticket and click Restore, or
  • Right-click the card and choose Restore.

From an AI agent: restore_ticket(ticket_id). The ticket lands in the column it was archived from. If that column has been deleted in the meantime, it lands in the project’s first column.

Bulk operations

You cannot bulk-archive from the UI in v1, but agents can sequence archive_ticket calls themselves (no bulk endpoint exists, since archive is rare enough that the per-ticket cost is acceptable).

When to archive vs. when to leave on the board

Some teams archive aggressively (Done is a transient state; once human review confirms the fix, archive). Others leave Done populated for reference and only archive truly stale tickets.

Both are fine. Toado does not enforce a workflow.

Cross-project moves vs. archive

If you accidentally captured into the wrong project, move the ticket rather than archiving. Cross-project moves within the same company are supported. See move_ticket in the tools reference or drag the ticket between project pickers in the UI.

Where to next