jira_get_issue
Retrieve detailed information about a Jira issue, including Epic links and relationships, with configurable fields and comments.
Instructions
Get details of a specific Jira issue including its Epic links and relationship information.
Args: ctx: The FastMCP context. issue_key: Jira issue key. fields: Comma-separated list of fields to return (e.g., 'summary,status,customfield_10010'), a single field as a string (e.g., 'duedate'), '*all' for all fields, or omitted for essentials. expand: Optional fields to expand. comment_limit: Maximum number of comments. properties: Issue properties to return. update_history: Whether to update issue view history.
Returns: JSON string representing the Jira issue object.
Raises: ValueError: If the Jira client is not configured or available.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| expand | No | (Optional) Fields to expand. Examples: 'renderedFields' (for rendered content), 'transitions' (for available status transitions), 'changelog' (for history) | |
| fields | No | (Optional) Comma-separated list of fields to return (e.g., 'summary,status,customfield_10010'). You may also provide a single field as a string (e.g., 'duedate'). Use '*all' for all fields (including custom fields), or omit for essential fields only. | description,updated,reporter,status,summary,assignee,issuetype,priority,created,labels |
| issue_key | Yes | Jira issue key (e.g., 'PROJ-123') | |
| properties | No | (Optional) A comma-separated list of issue properties to return | |
| comment_limit | No | Maximum number of comments to include (0 or null for no comments) | |
| update_history | No | Whether to update the issue view history for the requesting user |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |