Get full detail for one Jira issue as Markdown.

Returns summary, status, type, priority, resolution, assignee, reporter, labels, components, fix versions, created/updated timestamps, the full description, all non-empty custom fields (e.g. acceptance criteria, story points) with their display names, the attachment list (fetch images via get_attachment), and (by default) the complete comment thread.

Get only the comment thread of a Jira issue, as Markdown.

Each comment includes author, timestamp, whether it was edited, and any visibility restriction. Use this instead of get_issue when the ticket body is already known and only the discussion is needed.

Map the reference graph around a Jira issue: parent, subtasks, links.

Returns the parent (e.g. epic), all subtasks, and all linked issues — each resolved to key + type + status + summary so the next issue to read can be chosen without further calls. Link relationships are given in human terms with correct direction ("blocks" vs "is blocked by"). For epics, also lists the issues inside the epic.

Search Jira with a JQL query; returns a compact Markdown list.

Each result line has key, type, status, summary, assignee and last update. Example JQL: 'project = PROJ AND status != Done ORDER BY updated DESC'. Results are capped at limit (1-100); the output notes when more matches exist.

Download an image attached to a Jira issue, for visual analysis.

Returns the image itself so it can be looked at directly. Use it when a ticket's Attachments section (from get_issue) lists a screenshot or other image relevant to the task, e.g. a UI bug report where the screenshot shows the actual broken state.

Only images are supported (png, jpeg, gif, webp) up to 5 MB; videos and other file types are rejected with an explanatory error.

Report which Atlassian account this server is authenticated as.

Returns display name, email, account ID, and which base URL was selected (site URL vs cloud-ID fallback). Call this first when any other tool returns authentication or permission errors — it isolates whether the problem is the credentials or the specific resource.