create-release-note

Name

jira:create-release-note

Synopsis

/jira:create-release-note <issue-key>

Description

The jira:create-release-note command automatically generates bug fix release notes by analyzing Jira bug tickets and their linked GitHub pull requests, then updates the Jira ticket with the generated release note content.

This command is particularly useful for:

• Creating consistent, well-formatted release notes across all bugs
• Automatically extracting information from multiple sources (Jira + GitHub)
• Saving time by analyzing PR code changes, commits, and descriptions
• Ensuring complete release notes with Cause, Consequence, Fix, Result, and Workaround

The command follows the standard release note template format and populates both the Release Note Type and Release Note Text fields in Jira.

Implementation

The jira:create-release-note command runs in multiple phases:

🎯 Phase 1: Fetch and Validate Jira Bug

1. Fetch bug ticket using getJiraIssue MCP tool:

   • Request all fields to ensure we have complete data
   • Verify the issue is a Bug type
   • Extract issue description, links, and custom fields

2. Validate issue type:

   • If not a Bug, warn user and ask if they want to continue
   • Release notes are typically for bugs, but may apply to other types

3. Parse bug description to extract required sections:

   • Cause: The root cause of the problem
   • Consequence: The impact or effect of the problem

4. Handle missing sections:

   • If Cause or Consequence sections are missing, inform the user
   • Provide template format and ask user to update the bug description
   • Optionally, allow user to provide Cause/Consequence interactively

🔗 Phase 2: Extract Linked GitHub PRs

Extract all linked GitHub PR URLs from multiple sources:

1. Remote links (Primary source - web links in Jira):
   • Check the Jira issue response for web links/remote links
   • Common field names: remotelinks, issuelinks with outwardIssue.fields.issuetype.name == "GitHub PR"
   • Look for GitHub PR URLs in remote link objects
   • Pattern: https://github.com/{org}/{repo}/pull/{number}
   • Extract PR URLs and parse into {org}/{repo} and {number}