Ticket Lifecycle

Every ticket passes through up to three phases — Research, Planning, and Execution — in that order. Each phase produces a document that goes through draft → approval-requested → approved (or rejected). You can revise documents as many times as needed before moving on.

The phase model

You can start a ticket in any phase using Starting Phase on the create form. Skipping a phase records a workflow override on the ticket so reviewers can see why it happened. The default and recommended path is to start in Research for unknown issues and in Planning for well-defined ones.

Working a phase

When a phase finishes, its document appears in Draft state with a row of action buttons:

• View Job — open the job log that produced this document.
• Recreate Plan / Recreate Research — discard the current draft and re-run the phase from scratch.
• Revise — open a revision dialog where you write feedback. The agent runs again, this time with your feedback included as task instructions, and produces a new document version. Each revision is stored in the ticket history.
• Edit — open the document in an inline editor to make manual changes. Manual edits are tracked as revisions with source: manual so you can see who changed what.
• Request Approval — flip the document from Draft into Approval Requested. Use this when you are ready for someone (or yourself, on a different sitting) to formally approve the document.

Once a document is in Approval Requested state, the buttons change to:

• Approve Planning & Continue (or Approve Research & Continue) — mark the document as approved and unlock the next phase.
• Reject — send the document back to draft so it can be revised.

Approvals are recorded in an audit trail with the actor, optional comment, and timestamp.

Revision history

Every change to a phase document is captured. The system distinguishes between:

• Agent revisions — created when you click Recreate or Revise and the agent re-runs.
• Manual revisions — created when you edit the document in place.

You can scroll back through previous versions to compare wording, restore an earlier version, or audit who suggested what.

Approving and continuing

Approval is the gate that moves a ticket forward. The flow is:

1. Phase document is generated by the agent.
2. You read it. If anything is off, click Revise (with feedback) or Edit (to fix it manually).
3. Click Request Approval when the document looks right.
4. Click Approve … & Continue. The next phase tab unlocks and a new agent run starts immediately.
5. Repeat for the next phase until Execution finishes and a pull request is opened on your linked repository.

If you need to skip a phase entirely — for example, because you want to bypass approval and run execution immediately — use Force Execute on the ticket header. This records a workflow override (with reason, actor, and timestamp) on the ticket so the bypass is auditable.

Agent runs and the Jobs page

Every time a phase runs, a job is created. You can find every job in the project's Jobs page (sidebar → Jobs). Each row shows the status (Queued, Running, Completed, Failed), the job kind (Research, Planning, Execution, Claw), the ticket title, the repository, the duration, and when it was created. Click into a job to see the full agent log.

Tips

• Read the plan before approving execution. The plan is the cheapest place to catch bad ideas.
• Use Revise instead of Edit when you want the agent to learn from your feedback for the next iteration. Manual edits are good for typos and tweaks.
• Force Execute is a power tool — it bypasses the safety net of planning approval. Make sure the change is mechanical enough to skip review.
• Inspect the Jobs page if a phase seems stuck. Worker logs reveal cloning issues, missing secrets, and agent errors faster than the ticket page does.