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

# jstm ticket

> Read a run's work as tickets — the business-readable view of what an agent did.

Tickets are the same work as stories, presented for people rather than for the execution engine. A teammate can read a ticket list without knowing anything about the CLI's internals.

## `ticket list`

List tickets, grouped by run.

```bash theme={null}
jstm ticket list                                    # all your tickets
jstm ticket list --agent-id month-end-close
jstm ticket list --run-id 5f3a5c81-2d44-4e0b-9a17-0c9d3b7e9b21
jstm ticket list --mode live --status blocked --since 24h
```

| Option         | Default | Description                                                         |
| -------------- | ------- | ------------------------------------------------------------------- |
| `--run-id`     | —       | Show one run's tickets: its epic and stories                        |
| `--agent-id`   | —       | Show all runs for an agent                                          |
| `--mode`       | —       | Filter by `dry_run`, `pilot`, or `live`                             |
| `--status`     | —       | Filter by ticket status such as `open`, `in_progress`, or `blocked` |
| `--since`      | —       | Recency window, such as `15m` or `24h`                              |
| `--limit`      | `20`    | Maximum number of runs                                              |
| `--json`       | off     | Emit the raw payload                                                |
| `--out <file>` | —       | Write the JSON payload to a file                                    |

With no `--run-id` or `--agent-id`, you get all your tickets grouped by run.

## `ticket show`

Show a ticket's detail card, or an epic's story tree, with its run summary.

```bash theme={null}
jstm ticket show 8c41f2b9-77de-4a30-b0c5-2e1f6a9d4b77
jstm ticket show 8c41f2b9-77de-4a30-b0c5-2e1f6a9d4b77 --out ticket.json
```

| Option         | Description                      |
| -------------- | -------------------------------- |
| `--json`       | Emit the raw payload             |
| `--out <file>` | Write the JSON payload to a file |

Passing an epic id renders the whole tree of stories underneath it. Passing a story-level ticket id renders that one ticket's detail.

## Tickets and stories

They describe the same work from two angles.

|                                 | Answers                                                |
| ------------------------------- | ------------------------------------------------------ |
| Story, via `jstm agent stories` | How the agent understands and executes the work        |
| Ticket, via `jstm ticket list`  | How the organization sees, owns, and resolves the work |

Reach for tickets when you want to know what happened. Reach for stories when you want to know how it executed.

## See also

* [Runs and work](/concepts/runs-and-work) — runs, epics, stories, tickets.
* [Review runs and tickets](/guides/review-runs-and-tickets) — walkthrough.