list_tickets
Lists a project's tickets in plan order with status, dependencies, and blockers to identify ready work and determine the next ticket to handle.
Instructions
The project's tickets in plan order: id, label (the Linear identifier such as ENG-12, the
GitHub identifier such as GH-12, else T), title, status (todo, in_progress, done,
canceled), milestone, depends_on, the GitHub repo it changes (repo, owner/name, for a
project that spans several), whether it is ready (all it depends on is done) or which tickets
block it, the link when it lives in Linear or GitHub, and the id and title of each one's
working doc, and who it is for (assignee, {id, name}, or null with assignee_raw as the
source named them, and assignee_note: "assignee: Kiran" or "unowned (kiran@x.com is not on
this cell)"). Work the ready tickets in this order. Also says where they live: linear is
the Linear project and github the repo and issue label, each with when it was last synced
(null when the project does not use it); with both null the tickets live in Tares. Read one
with get_ticket to get its working doc.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "list_tickets"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |