Manage tickets without prescribing a workflow

Open a board to create tickets in the lane that best represents their current place. Use the title for the outcome, the description for enough context to act, and the ticket kind to distinguish ordinary work from Features, Epics, Bugs, Research, or Action Items. Use the Kanban view to reorder work. Use the sortable Table view to compare tickets across the current board or lane without changing their saved order.

Board filters stay selected when you change projects, switch layouts, reload the page, or use another open tab. Status and priority filters apply everywhere. An assignee or creator filter applies only in projects where that person is a member. ToDoddle labels the saved selection Unavailable in this project elsewhere, so it does not hide the current project's tickets. Use Clear All to reset the filters.

Open the filter panel to use a quick filter for common views: My open, Unassigned, Needs review, Due soon, or Blocked. Due soon covers open tickets due within seven calendar days, including today. A quick filter replaces the detailed filter selections. If you change a detailed filter afterward, ToDoddle labels the result Custom. Clear all returns to the full board.

The create form uses the same Markdown description tools as ticket editing. It also accepts files and Replay before the ticket exists. After creation, ToDoddle opens the new ticket on its full page with editing active. Existing tickets still open in quick view from a board. Quick view expands to use the available screen space. Wide screens show ticket details and attachments beside discussion and activity. Smaller screens stack the same areas in one scrollable view.

Use Delete attachment on a ticket file to remove it after confirmation. ToDoddle keeps the file when another ticket, comment, or project feature still uses it. If storage is unavailable, the attachment remains on the ticket and you can retry.

Each normal opening of the create form starts a new draft. It clears the prior title, description, assignment, due date, kind, parent, and pending files. Returning from an active Replay restores that recording's draft instead.

Status and lane are separate signals. Teams may use lanes as workflow stages, functional groupings, or time horizons. If a lane has entry actions, moving a ticket into it can update fields automatically; ToDoddle shows the resulting authoritative ticket and any warnings.

Useful ticket relationships include:

• Parent and children for decomposition inside one board.
• Blocked by for a real delivery dependency.
• Context links for specifications, decisions, research, or evidence.
• Watchers for people who want updates without owning the ticket.
• Checklist for small shared completion steps.
• Attributes for bounded typed facts such as a repository or delivery environment. Never put credentials or other secrets in an attribute.

Use comments for questions, decisions, progress, and verification. Reply to keep a response with its comment thread. Type @ or use Mention to notify an accessible person or Agent Connection. Authors can edit their own comments. Attach a file or record a Replay when the artifact belongs with the ticket discussion. A human assignee, a durable Agent assignment, and a temporary Agent Connection claim are separate signals.

Archive work when it should leave normal views without being permanently deleted. Archived tickets and lanes can be restored from Show Archived on the active board. Completing or archiving a ticket stops its open timers; reopening or restoring permits new timing again.

Use Complete when the work produced its intended result. Use Closed when work ended for another reason, then record the required reason and any duplicate or explanatory note. Both states leave active work and stop open timers, but closed work remains available in filtered history. Reopening a closed ticket clears its closure record.

For meaningful work, finish with a concise verification comment and the correct terminal status. A status change is not a substitute for evidence that the requested behavior works.