two-node:create-rhel-stories

Automating OCPEDGE story creation from RHEL verification tickets involves grouping related issues, generating summaries, and creating missing backlog stories using a JQL query or specific ticket keys.

Grouping related RHEL tickets works by parsing ticket summaries, clone relationships, and shared references to deterministically cluster issues before generating consistent Jira-ready OCPEDGE stories and descriptions.

Yes, you can preview Jira story creation for TNF RHEL tickets by running the command with the --dry-run flag, which generates a planning overview that requires explicit approval before creating any OCPEDGE stories or subtasks.

Yes, you need Jira access configured via the mcp-atlassian MCP tools to search RHEL tickets, assign components, create verification and automation subtasks, and add Relates links between the tickets and stories.

The best way to link untested RHEL TNF tickets to OCPEDGE backlog stories is to use an automated workflow that detects missing stories, groups tickets by shared references, and applies Relates links during the story creation process.

RHEL TNF verification tickets may be missing OCPEDGE backlog stories because they have not been grouped and processed by the story creation workflow, which detects untested tickets and generates the required parent stories and subtasks.