| 1 | --- |
| 2 | title: The Board |
| 3 | description: The workspace's backlog as it moves, in five stages from Backlog to Done. Each work item's stage follows from what is true of it, its claims, sessions, pull requests and landings, so there is nothing to drag. |
| 4 | --- |
| 5 | |
| 6 | **Board**, in Work's sidebar, at `g1t.sh/<workspace>/-/work/board`, is |
| 7 | the backlog as it moves. Its columns are stages, and a work item's stage |
| 8 | comes from what is true of it: who is on it, its pull requests, where it |
| 9 | has landed. There is nothing to drag. Do the work, and the card moves. |
| 10 | |
| 11 | ## The stages |
| 12 | |
| 13 | | Stage | Holds the work items | |
| 14 | | --- | --- | |
| 15 | | **Backlog** | Open, and nobody is on it. | |
| 16 | | **In progress** | Claimed or assigned, with a live session on it, or with a draft pull request. | |
| 17 | | **In review** | With a pull request open for review. | |
| 18 | | **Landing** | Landed in some of its target repositories, still missing in others. | |
| 19 | | **Done** | Closed in the last 14 days. | |
| 20 | |
| 21 | A work item is in the first stage that holds for it, in the order |
| 22 | **Done**, **Landing**, **In review**, **In progress**, **Backlog**. So a |
| 23 | work item with one pull request in review and another still a draft is |
| 24 | **In review**, and one that has landed in one of its two targets is |
| 25 | **Landing** whatever else is going on. A work item closed more than 14 |
| 26 | days ago leaves the Board; the Work list's **Closed** still has it. |
| 27 | |
| 28 | ## How a work item moves |
| 29 | |
| 30 | A typical work item goes left to right as the work happens: |
| 31 | |
| 32 | 1. **Backlog.** Someone files it. Nobody has claimed it, it has no |
| 33 | assignee, no session is on it and it has no pull request. |
| 34 | 2. **In progress.** Someone [claims it](/work/claims-and-dependencies/#claims) |
| 35 | (`g1t work claim 12`), it is assigned, a [session](/work/sessions/) |
| 36 | starts on it, or a draft pull request is opened for it |
| 37 | (`g1t pr create --item 12` opens a draft). A pull request a live session |
| 38 | is on counts too. |
| 39 | 3. **In review.** Its pull request is marked ready for review. |
| 40 | 4. **Landing.** For a work item with several targets: its pull request |
| 41 | merged in one repository and the others are still to land. A work item |
| 42 | with no target, or one, skips this stage: it closes as soon as it lands. |
| 43 | 5. **Done.** It closed: every target landed, or someone closed it. See |
| 44 | [closing work items](/work/closing/). |
| 45 | |
| 46 | It moves back as well: a claim released or expired with nobody else on it |
| 47 | and no pull request sends it back to **Backlog**, and reopening a work item |
| 48 | clears where it landed, so it goes back to whatever stage its pull |
| 49 | requests and claims put it in. |
| 50 | |
| 51 | ## Reading the Board |
| 52 | |
| 53 | Each column lists its work items most recently changed first, and **Done** |
| 54 | most recently closed first. Each card shows the work item's title, number |
| 55 | and repositories, and who is on it: up to three people (its assignees, |
| 56 | whoever claimed it, whoever runs a session on it), up to two of its live |
| 57 | sessions, then "+2" for the rest. Choose a card to open the work item. |
| 58 | |
| 59 | The Board follows the work as it happens, without reloading, and checks |
| 60 | again every 30 seconds while a session is live, since a session going idle |
| 61 | sends no event. |
| 62 | |
| 63 | - **One repository's**: filter it with `?repo=<name>`. **Board** on the |
| 64 | Work list filtered to a repository keeps the filter. |
| 65 | - **On a phone** the Board shows one stage at a time, with a button for |
| 66 | each and how many it holds; the address keeps it as `?stage=landing`. |
| 67 | - **In the phone app**, **Board** at the top of Work shows the stages one |
| 68 | under another, with a chip for each to show one alone. |
| 69 | |
| 70 | **New work item** is on the Board too. |