Filing a ticket
draftA ticket is what you want done, in a project. Filed, it waits in the backlog until you start its pipeline; started, it queues for its project’s slot (Projects, tickets and the queue).
New ticket
Section titled “New ticket”New ticket, at the top of every screen:
| Field | What it is |
|---|---|
| Type | Bug or feature |
| Title | One line |
| Body | Markdown. Open in panel writes it at full size, with a preview beside it |
| Attachments | Files every step reads. See below |
| Assignee | Who it is assigned to. An open ticket assigned to you with no run shows in your inbox |
| Runner | Optional: a runner label, or one runner, to pin every step of its run to |
Start pipeline when its turn comes starts its run as it is filed. What you typed is kept in the browser until you file it.
What the agents read first
Section titled “What the agents read first”enrich and plan, the first two steps, start from the ticket’s title, body and files. enrich investigates the request in the code and writes the spec; plan turns it into a plan and the acceptance criteria. Neither has anything else to go on: what is not in the ticket, they look for in the repository, or ask you (Answering agents).
This page does not yet say what makes a ticket good: nothing in Pitwall has measured it.
Attachments
Section titled “Attachments”Images, text, Markdown, HTML, PDF or a zip, up to 50 MB each. Every step of the ticket’s pipeline reads them:
- a zip is extracted;
- a Claude Design export is split into its screens;
- a screenshot is read as an image.
A file’s bytes are kept for PITWALL_FILE_RETENTION_DAYS, 365 days by default; after that the ticket says the file was removed. Your settings → Storage shows what takes space, and deletes a file.
From a phone: Capture
Section titled “From a phone: Capture”Capture, at /capture, files a bug in a few taps: a project, a title, an optional note, and photos from the camera. The project is remembered on that device.
Starting and following a run
Section titled “Starting and following a run”Open the ticket and click Start pipeline. The tracker shows each step with its model, effort, tokens and cost; the timeline shows the agent’s events as they arrive. Both refresh on their own.
| On the ticket | Does |
|---|---|
| Resume | Restarts a blocked run, with more token budget when it ran out |
| Close run | Once the run waits with no open pull request: finishes the ticket’s work and frees the project’s slot |
| Cancel run | While it has no open pull request |
A ticket whose run is done is not started again. More work on it is a linked bug or a new ticket.
Board shows every ticket across your projects in five columns: Backlog, Queued, Running, Needs you and Done.