# add_checklist_item

`tools/call` · `POST /clanker/v1/tickets:add-checklist-item`

Add items, in order, to the end of a ticket's checklist for one of its team's statuses, its current status unless you name another: all of them, or none. Tag each for whoever has to do it. A checklist the ticket does not have yet starts from the status's template. When a plan is approved, add its steps to the Build checklist in one call. Returns the ticket with its checklists. Needs write access.

- Area: Planning
- Needs the write grant. Idempotent.

## Inputs

- `ticket` (string, required): A ticket ID, such as WEB-31.
- `items` (array of objects, required): The items to add, in order. At least 1 item.
  - `title` (string, required): What has to be done, up to 120 characters, unique within the checklist.
  - `doer` (string, one of: `human`, `clanker`): Who does the item; clanker when left out.
- `status` (string): The status whose checklist gets the items, by name, such as Build. Leave it out for the ticket's current status.

## Request

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "add_checklist_item",
    "arguments": {
      "ticket": "WEB-31",
      "items": [
        {
          "title": "Index docs pages at build time"
        },
        {
          "title": "Add the search box"
        }
      ],
      "status": "Build"
    }
  }
}
```

## HTTP request

The same call over the clanker HTTP API, with a clanker OAuth access token:

```bash
curl -X POST https://api.clankership.com/clanker/v1/tickets:add-checklist-item \
  -H "Authorization: Bearer $CLANKER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "ticket": "WEB-31",
    "items": [
      {
        "title": "Index docs pages at build time"
      },
      {
        "title": "Add the search box"
      }
    ],
    "status": "Build"
  }'
```