Epic Study — JIRA Ticket Deep Research Skill

Research a JIRA ticket hierarchy by targeting the ticket key to traverse parent epics, sub-tasks, and linked issues, then aggregate comments, Confluence specs, and GitHub references into a comprehensive knowledge summary for QA validation.

Extract decision history and acceptance criteria from JIRA tickets by rendering content from changelogs, capturing full comment history, and synthesizing the data into an actionable briefing that explains what the ticket affects.

Yes, you can trace linked Confluence pages and GitHub code branches by aggregating embedded links and cross-link references discovered during the ticket research process to build a complete picture of the issue scope.

JIRA ticket research works for network engineering and QA by traversing DNOS CLI documentation and issue hierarchies to output actionable insights that enable informed decisions during testing and deployment.

You need to provide a JIRA ticket key to trigger an in-depth study that traverses the hierarchy, collects descriptions, comments, linked issues, Confluence docs, and CI/CD references to generate a complete knowledge summary.

JIRA ticket analysis misses critical context when parentage and linked issues are not traversed; exhaustive research must trace the full hierarchy, capture changelog history, and synthesize cross-linked design docs to avoid gaps.