jira_get_issue
Retrieves a Jira issue by key or ID, returning system fields and populated custom fields, with options to include comments, worklogs, attachments, or request specific custom fields.
Instructions
Get an issue: system fields plus custom fields that currently have a value, each as {id, name, value}. Comments, worklogs, and attachments are omitted unless include lists them. Null custom fields are omitted unless customFields is "all". To fetch specific custom fields (including empty ones), pass fields as customfield_ ids or unique edit-screen names (Severity). Call jira_get_edit_meta to see writable fields; do not call jira_get_fields for an update.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"issueKey": "<issueKey>"
},
"name": "jira_get_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| expand | No | Jira expand values in addition to names (e.g., changelog, renderedFields) | |
| fields | No | Narrow custom-field GET. Ids (customfield_11205) or unique editmeta names (Severity). Replaces *navigable for custom fields; requested fields are returned even if null. | |
| include | No | Collections to include. Default omits comments, worklogs, and attachments. | |
| issueKey | Yes | Issue key (e.g., KP-123) or numeric issue ID | |
| customFields | No | set (default): only custom fields with values. all: include navigable custom fields that are null. |