added 2026-09-30
Show the change history (audit trail) of an issue, newest first and all of it, page by page (no entry is out of reach): what changed (field, from → to), who did it, through which client (web, mcp, api…) and when. Comment text is never included; description edits show only the version number, which get_description_version reads. 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.
cursorstringoptionalCursor from `Next page` of an earlier result of this call (omit for the first page); pass it unchanged, with the same other argumentsformatenumoptionalAnswer format: "json" (default) is one compact JSON document; "text" is a readable Markdown answerjsontextkeystringrequiredIssue key, e.g. ITR-12limitintegeroptionalHow many entries per page (1–500, default 50)
Returns
One of these shapes, depending on the arguments:
Shape 1
countintegerrequiredhistoryarray of object | nullrequiredlimitintegerrequired
Shape 2
Optional fields, when present
cursorstringoptionalnotestringoptionalpageintegeroptionalpagesintegeroptionaltotalintegeroptionaltotalApproximatebooleanoptional
- 2026-10-02 — Answers are compact JSON by default (one document, no Markdown, nothing said twice); format="text" gives the readable Markdown without the json block. Each entry is {at, field, by (username), via, from, to} (from / to absent when empty; comment entries have neither).
- 2026-10-02 — New optional cursor argument (limit existed): the history is read page by page, newest first. The answer carries the paging (total, totalApproximate, page, pages, count, limit, cursor; a missing cursor means the last page); format="text" opens with a header (Page N of M · X items · showing a–b) and ends with the next cursor or Last page.
- 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.