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.

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.

Use comments for questions, decisions, progress, and verification. Attach files when the artifact belongs with the ticket discussion. A human assignee represents accountability; a visible Agent Connection claim represents temporary automated execution. They can coexist.

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.

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.