search_issues

Find issues by text and filters (status, type, priority, category, open, assignee, reporter, label, parent, epic, story, orphans, subtasks, blocked, due, subscribed; the list filters take one value or an array and match any of them). Omit project to search every accessible project. The json answer has the paging (total, totalApproximate when it is a lower bound, page, pages, count, limit, cursor), `statuses` ({key: {name, category}} for the statuses of the page; when projects of one answer give a key different meanings it is PREFIX/key, in the map and in the rows) and `issues` (key, title, type, status key, priority, assignee, parent, blocked; fields adds more).With in_comments=true (needs project and query) the search also reads the comments: `hits` are ranked, each with the issue key and either `comment` (its id, the reply_to of add_comment) or `in` (title / description), and a snippet; sort and order do not apply; approximate: true means the text is so common that the hits are the most recent matches, not ranked; a one-character query matches titles by prefix only. Answers are compact JSON; pass format="text" for a readable Markdown answer. Results are paged: if the answer has a cursor, call again with it (a missing cursor means the last page) — never assume the first page is everything.

• 2026-10-05 — New week (this, next, last or a YYYY-MM-DD day) and committer filters: the issues somebody committed to for a week (set_commitments); fields also takes committers.
• 2026-10-05 — New optional cycle filter: current, next, none, any or a cycle number (one project); fields also takes cycle (its number).
• 2026-10-04 — New reviewer and review_state filters: the issues somebody is asked to review (set_reviewers).
• 2026-10-03 — New optional blocked filter (true: issues with an open blocker, false: without); each issue in the json block has a blocked flag, and a blocked issue's line says `· blocked`.
• 2026-09-28 — New dir argument (asc or desc) sets the sort direction.
• 2026-10-01 — New optional cursor argument: pass the cursor a result ends with to get the next page.
• 2026-10-01 — New optional reporter and subscribed filters; in_comments (with project and query) also searches the comments and returns ranked hits with comment ids and snippets.
• 2026-10-01 — in_comments results end with a ```json block (count, cursor, approximate); approximate is true when a very common search text returned the most recent matches instead of the ranked best ones.
• 2026-10-01 — A very common search text caps the total of the first page: the json block adds total_approximate: true and total is a lower bound (a status counts at most 1001); selective texts stay exact.
• 2026-10-01 — New optional due filter (overdue, week, none, any) and sort=due; results show each issue's due date.
• 2026-10-01 — Every filter of the web list is here: priority, category, open, label (names), parent, epic, story, orphans and subtasks; status, type, assignee and project take one value or a list; assignee and reporter usernames work without project (among the people you share a project with). The result now ends with a ```json block (total, count, cursor and, per issue, key, title, type, status key / name / category, priority, assignee, reporter, due, updated, parent).
• 2026-10-02 — The total of a long result is counted once, up to 1000 (total 1000 with totalApproximate: true: a lower bound, header `1000+ issues`), for every search text, and every page carries it; the json block now has totalApproximate, page, pages and limit and total on every page. An out-of-range limit reads 25 and the result says so. New optional page argument jumps to page N of the result (the same limit and other arguments; at most 10000 rows deep, a deeper page is the error page_out_of_range; a cursor wins over page); the cursor of that page continues with page N+1. parent also takes none (only issues without a parent). sort also takes status (the board's order of statuses) and assignee (by name, the unassigned last).
• 2026-10-02 — Answers are compact JSON by default (one document, no Markdown, nothing said twice); format="text" gives the readable Markdown list (header, rows, Next page / Last page., no json block). JSON issues have key, title, type, status (the key only), priority (absent when none), assignee (username, absent when none), parent (key, absent when none) and blocked (only when true); the `statuses` map ({key: {name, category}}) says what the status keys on the page mean; optional fields adds updated, created, reporter, due, labels, status_name. The paging is flat in the document ({total, totalApproximate, page, pages, count, limit, cursor, note}); a missing cursor means the last page, and total_approximate is gone. in_comments hits are {key, comment | in, snippet}. Clients that parsed the ```json block: read the document itself, or pass format="text" to keep the old Markdown.
• 2026-10-03 — New optional view: a saved view id (list_views) runs its project, filters and sort (sort / order still win; other filters are refused). The answer has view {id, name, mode, stale, note}; a view that lost a whole filter fails (view_stale).
• 2026-10-04 — reporter=<username> with a project also finds issues reported by a former member of it (anyone who reported an issue there); assignee still needs a member.
• 2026-10-03 — New optional ac_incomplete / dod_incomplete filters (true: only issues with unchecked acceptance criteria / definition of done items, in projects that have the list on).
• 2026-10-03 — An issue with criteria has ac / dod {done, total} in its json row and `· AC 2/3 · DoD 0/1` in its text line.
• 2026-10-03 — Also answers structuredContent (see outputSchema); a failed call adds structuredContent.error. Text unchanged. Details: /docs/mcp, "Structured results and errors".
• 2026-10-04 — Claude Code 2.1.288+ (clientInfo claude-code): the text of a successful answer is itself up to 512 bytes, else "Result in structuredContent (N bytes)."; structuredContent and errors are unchanged. See /docs/mcp.
• 2026-10-04 — format="text" now also answers structuredContent {"text": the Markdown} (it was the JSON document), so a client that reads only structuredContent gets the Markdown it asked for.