> ## Documentation Index
> Fetch the complete documentation index at: https://docs.building58.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tickets, tasks and the Board in Building58

> How work moves through a Building58 room: the columns a ticket passes through on the Board, what a task is, and which steps need you and which can run alone.

In Building58, a ticket is work that exists before anyone starts on it. A task is a ticket being built: a copy of the repo, a branch and a Dev. The Board shows every ticket in the column for where its work is.

## A ticket's life

**1. Triage**

The PM or a worker filed it, and no person has looked at it yet. It waits for you to approve or reject it.

**2. Ready**

You approved it, or you filed it yourself with **Add ticket**, which skips Triage. It starts when you press **Start**, when a Lead you allowed starts it, or when Autopilot picks it up.

**3. Building**

It has a task: a copy of the repo, a branch and a Dev. It stays here after the Dev opens a pull request.

**4. In review**

Usually, the pull request is up.

**5. Changes requested**

The work went back for fixes, from you or from a review.

**6. Waiting on you**

Something only you can do: answer a Dev, merge a pull request only you may merge, or pick up a task Autopilot handed to you.

**7. Done**

You marked the task Done. With Autopilot on, it marks a task Done once its pull request has merged.

Without Autopilot, nothing moves a ticket past Building on its own, not even a pull request being opened or merged. The one exception: when the relay tells a Dev about review comments, it moves the task to Changes requested.

## Where a task works

A task's copy is `<repo>/.worktrees/<name>`, on the branch `task/<name>`. Your own folder does not change. The copy also gets a stub `.env` with no real keys and ports of its own, so tests in two copies do not collide.

When the work is done, stop the Dev and press **Clean up** on the task. It removes the copy and keeps the branch.

## Order and limits

* Each card has a priority: high, normal or low. Cards go high first, then in work order. You set priority and order, and so can a PM or Lead you allow.
* Up to 3 tasks are built at once unless you change the limit, and a room has 9 desks.
* A ticket can wait for others. It cannot start until every ticket it waits for is done.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.