jira_get_issue
Retrieve detailed Jira issue information, including Epic links, relationships, and optional fields like comments or changelog, using the MCP Atlassian server integration.
Instructions
Get details of a specific Jira issue including its Epic links and relationship information
Input Schema
Name | Required | Description | Default |
---|---|---|---|
comment_limit | No | Maximum number of comments to include (0 or null for no comments) | |
expand | No | Optional fields to expand. Examples: 'renderedFields' (for rendered content), 'transitions' (for available status transitions), 'changelog' (for history) | |
fields | No | Fields to return. Can be a comma-separated list (e.g., 'summary,status,customfield_10010'), '*all' for all fields (including custom fields), or omitted for essential fields only | summary,description,status,assignee,reporter,labels,priority,created,updated,issuetype |
issue_key | Yes | Jira issue key (e.g., 'PROJ-123') | |
properties | No | A comma-separated list of issue properties to return | |
update_history | No | Whether to update the issue view history for the requesting user |
Input Schema (JSON Schema)
You must be authenticated.
Other Tools from MCP Atlassian
- confluence_attach_content
- confluence_create_page
- confluence_delete_page
- confluence_get_comments
- confluence_get_page
- confluence_get_page_ancestors
- confluence_get_page_children
- confluence_search
- confluence_update_page
- jira_add_comment
- jira_add_worklog
- jira_create_issue
- jira_delete_issue
- jira_download_attachments
- jira_get_agile_boards
- jira_get_board_issues
- jira_get_epic_issues
- jira_get_issue
- jira_get_project_issues
- jira_get_sprint_issues
- jira_get_sprints_from_board
- jira_get_transitions
- jira_get_worklog
- jira_link_to_epic
- jira_search
- jira_transition_issue
- jira_update_issue
Related Tools
- @1broseidon/mcp-jira-server
- @sooperset/mcp-atlassian
- @zereight/confluence-mcp
- @CamdenClark/jira-mcp
- @sooperset/mcp-atlassian
- @sooperset/mcp-atlassian