Back to Details

do-tickets

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

do-tickets

do-tickets

A ticket is a unit of work in 
sesh
. When one is bound to your thread it's assigned to you; its prompt is your instructions. Loop: find → read → report.
Statuses: 
triage
(draft) → 
ready
(final, unattached) → 
active
(assigned to a thread) → 
done
/ 
dropped
(terminal). An 
active
ticket on your thread = your work; mark it 
done
when finished.
bash
undefined
一个ticket是
sesh
中的工作单元。当它绑定到你的线程时，就表示已分配给你；它的prompt就是你的工作说明。流程：查找→阅读→报告。
状态：
triage
（草稿）→ 
ready
（最终版，未绑定）→ 
active
（已分配到线程）→ 
done
/ 
dropped
（已结束）。你线程中的
active
ticket就是你的工作任务；完成后标记为
done
。
bash
undefined

FIND — your thread's tickets (auto-detected via the pane marker / $SESH_THREAD_ID)

FIND — 你的线程工单（通过面板标记/$SESH_THREAD_ID自动识别）

sesh ticket list --current # id status name thread sesh ticket list --current --json # one JSON object per line
sesh ticket list --current # 列：id status name thread sesh ticket list --current --json # 每行一个JSON对象

READ — the instructions (raw, no trailing newline)

READ — 查看工作说明（原始内容，无末尾换行）

sesh ticket get --id <id> --field prompt # --field: id|name|prompt|status|thread|created|closed|notes sesh ticket get --id <id> --json # whole record
sesh ticket get --id <id> --field prompt # --field可选：id|name|prompt|status|thread|created|closed|notes sesh ticket get --id <id> --json # 获取完整记录

REPORT — close AND record what you did, in one call (ALWAYS leave a note on close)

REPORT — 关闭工单并记录操作，一步完成（关闭时务必留下备注）

sesh ticket set-status --id <id> --status done --note "what you did; closed by <commit-sha>" sesh ticket set-status --id <id> --status active --thread <thread-id>

**Always leave a note when you close a ticket.** A ticket has a free-text **`notes`**
field; when you mark a ticket `done` (or `dropped`), append a short note explaining what
you did and — if there was a commit — which commit closed it. **Write notes in markdown**
(headings, lists, fenced code, links) — they are rendered as markdown in the Obsidian
ticket-note panel where Lukas reads them during consolidation. `--note` on `set-status`
appends as part of the same call (each `--note` appends, blank-line separated). You can
also append/replace notes independently:

```bash
sesh ticket set --id <id> --append-note "investigated; root cause is X"   # append
sesh ticket set --id <id> --notes "<full text>"                          # REPLACE
sesh ticket get --id <id> --field notes                                  # read them back
--id
takes the full ticket UUID (from 
ticket list
). Commands auto-route to wherever the ticket lives, so acting on your own thread's tickets just works.
A prompt may reference files/images as 
@blob(<hex>)
 tokens. When the prompt is delivered to you (
send-prompt
) these are already expanded to real paths you can read. If you read the prompt raw with 
ticket get --field prompt
, the tokens are NOT expanded — pipe through 
sesh blob expand
to resolve them to paths:
bash
sesh ticket get --id <id> --field prompt | sesh blob expand   # @blob(..) → real file paths
Other ops: 
ticket create --name <n> [--prompt <t>]
, 
ticket set --id <id> [--name|--prompt|--notes|--append-note]
, 
ticket send-prompt --id <id>
(type the prompt into the bound thread's pane), 
ticket delete --id <id>
. (
sesh ticket --help
for the rest.)
sesh ticket set-status --id <id> --status done --note "你的操作内容；由<commit-sha>关闭" sesh ticket set-status --id <id> --status active --thread <thread-id>

**关闭工单时务必留下备注。** ticket包含一个自由文本的**`notes`**字段；当你将工单标记为`done`（或`dropped`）时，添加简短备注说明你完成的工作——如果有提交记录，注明是哪个提交关闭了工单。**备注请使用markdown格式**（标题、列表、代码块、链接）——这些备注会在Obsidian的工单备注面板中以markdown渲染，供Lukas在合并时查看。`set-status`命令中的`--note`参数会在同一调用中追加备注（每次`--note`都会追加，以空行分隔）。你也可以独立追加/替换备注：

```bash
sesh ticket set --id <id> --append-note "已排查；根本原因是X"   # 追加备注
sesh ticket set --id <id> --notes "<完整文本>"                          # 替换备注
sesh ticket get --id <id> --field notes                                  # 查看备注
--id
需要传入完整的ticket UUID（来自
ticket list
命令）。命令会自动路由到工单所在位置，因此处理你自己线程的工单无需额外配置。
提示内容中可能会以**
@blob(<hex>)
令牌引用文件/图片。当提示内容交付给你时（通过
send-prompt
命令），这些令牌已被扩展为你可以读取的真实路径。如果你使用
ticket get --field prompt
读取原始**提示内容，令牌不会被扩展——可以通过管道传递给
sesh blob expand
来解析为真实路径：
bash
sesh ticket get --id <id> --field prompt | sesh blob expand   # @blob(..) → 真实文件路径
其他操作：
ticket create --name <n> [--prompt <t>]
（创建工单）、
ticket set --id <id> [--name|--prompt|--notes|--append-note]
（修改工单）、
ticket send-prompt --id <id>
（将提示内容输入到绑定线程的面板中）、
ticket delete --id <id>
（删除工单）。其余命令可查看
sesh ticket --help
。