CNTRLPLANE-1773: Add create-release-note command for automated bug fix release notes #99
Conversation
Add new command to automatically generate bug fix release notes by analyzing Jira bugs and their linked GitHub PRs. The command extracts Cause and Consequence from the bug description, analyzes PR content, and updates the Jira ticket with a synthesized release note. This automation saves time and ensures consistent release note quality across all bugs by analyzing multiple sources: PR descriptions, commit messages, code changes, and PR comments. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Add detailed implementation skill providing step-by-step guidance for generating release notes. The skill covers: - Parsing bug descriptions for Cause/Consequence - Extracting and analyzing GitHub PRs - Synthesizing information into cohesive release notes - Security validation and error handling This skill ensures consistent, high-quality implementation of the create-release-note command. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Add documentation for the new create-release-note command to the Jira plugin README. Includes usage examples, prerequisites, and sample output. This helps users understand how to use the new release note generation feature. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
Update PLUGINS.md and docs/data.json to reflect the new create-release-note command. Generated files are kept in sync with plugin metadata to ensure accurate documentation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
@bryan-cox: This pull request references CNTRLPLANE-1773 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@bryan-cox: This pull request references CNTRLPLANE-1773 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
approved
|
@bryan-cox: This pull request references CNTRLPLANE-1773 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
1 similar comment
|
@bryan-cox: This pull request references CNTRLPLANE-1773 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
Hm, when it went to github it assumed the jira key was github issue: Perhaps it can be coached a little better on now to find the linked PR's from the jira ticket? I used https://issues.redhat.com/browse/OCPBUGS-54412 -- which has a linked PR in the bug itself. But otherwise I like the output it eventually produced once it found the PR (it resorted to using |
Address feedback from @stbenjam to improve GitHub PR discovery logic: - Add explicit warnings against using `gh issue view` with Jira keys - Prioritize searching Jira remote links first (primary source) - Add fallback search using `gh pr list --search` for common repos - Provide user confirmation workflow for found PRs - Update both command and skill documentation with clear examples This prevents the error where the command tried to use Jira keys as GitHub issue numbers, which fails because they are different identifiers. Fixes: openshift-eng#99 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
|
@stbenjam Thanks for testing and the feedback! I've updated the PR discovery logic to address the
The command now correctly extracts PR URLs from Jira's web links first, and only falls back to searching if no links are found. This prevents the confusion between Jira keys and GitHub issue numbers. Updated files:
AI-assisted response via Claude Code |
3 participants
What this PR does / why we need it:
This PR adds a new
/jira:create-release-notecommand to automatically generate bug fix release notes by analyzing Jira bug tickets and their linked GitHub pull requests.Bug fix release notes require extracting information from multiple sources (Jira ticket fields and GitHub PR analysis). This command automates the process by:
Key Features:
Files Added:
plugins/jira/commands/create-release-note.md- Command definition with comprehensive documentationplugins/jira/skills/create-release-note/SKILL.md- Detailed implementation guidanceFiles Modified:
plugins/jira/README.md- Added command documentationPLUGINS.md- Generated plugin list (viamake update)docs/data.json- Generated website data (viamake update)Example Usage:
The command will:
Which issue(s) this PR fixes:
Fixes CNTRLPLANE-1773
Special notes for your reviewer:
make lint✓)gh) for data retrievalPrerequisites for testing:
gh) installed and authenticatedChecklist:
🤖 Generated with Claude Code via
/jira:solve [CNTRLPLANE-1773](https://issues.redhat.com//browse/CNTRLPLANE-1773)Co-Authored-By: Claude [email protected]