researching-jira-issues

name

researching-jira-issues

description

Use whenever the user mentions a Jira issue key and wants more than a surface-level lookup — "Read PROJ-123", "What's PROJ-123 about?", "Give me context on PROJ-123", "Deep dive PROJ-123", "What's blocking PROJ-123?", "Summarize PROJ-123 and its dependencies", "I need to work on PROJ-123, what should I know?", or any request to understand an issue's purpose, scope, or requirements. Thoroughly researches and synthesizes a Jira issue including all linked issues, sub-tasks, blocked dependencies, and supporting Confluence documentation.

Researching Jira Issues

Synthesize information, don't concatenate tool outputs. Each step below gathers raw data — the value of this skill is in connecting the dots across issues, docs, and comments into a coherent understanding that a human can act on.

Workflow

Step 1: Fetch the Main Issue

Use the get_issue MCP tool with the issue key. The tool defaults to expanding renderedFields and names, which provides HTML-rendered fields and human-readable custom field display names.

Extract and note:

• Issue type (Epic, Story, Task, Bug, Sub-task, etc.)
• Summary and description
• Current status and priority
• Assignee and reporter
• Key fields relevant to understanding the work (labels, components, sprint, etc.)
• Comments that provide important context (clarifications from stakeholders, technical decisions, implementation guidance)
• Custom fields: Surface all non-null custom fields from the Additional Fields section of the response. The names expansion maps field IDs to human-readable display names automatically.

Step 2: Identify All Linked Issues

Examine the main issue response to identify linked issues through:

1. Issue Links: Look for the issuelinks field in the API response (an untyped array field returned by Jira) containing: