JIRA Ticket Creator

Create JIRA tickets with required fields from user prompts.

5|17|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins --skill jira-ticket-creator-openshift-hyperfleet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: JIRA Ticket Creator
Source: https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins/tree/main/hyperfleet-jira/skills/jira-ticket-creator
Command: npx skills add https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins --skill jira-ticket-creator-openshift-hyperfleet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual JIRA ticket creation often leads to inconsistent structures and missing required fields like What, Why, and Acceptance Criteria. This skill standardizes ticket generation and enforces best practices across stories, tasks, bugs, and epics.

Core Features & Use Cases

  • Guided templates that enforce required sections (What, Why, Acceptance Criteria, Story Points, Activity Type)
  • Support for multiple issue types (Story, Task, Bug, Epic) with easy epics linkage
  • Quick generation from natural language prompts with post-create refinement in the web UI

Quick Start

Ask the assistant to generate a JIRA ticket using the standard What/Why/Acceptance Criteria template whenever you request to create a ticket, story, task, or epic.

Frequently Asked Questions about JIRA Ticket Creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Jira ticket creation from natural language prompts?

You can automate Jira ticket creation by providing a natural language prompt that the assistant parses to generate a structured issue. The skill validates input and applies configured templates to ensure required sections like What, Why, and Acceptance Criteria are populated.

What is the best way to structure Jira epics and stories with required fields?

The best way to structure Jira epics and stories is using guided templates that enforce required fields. This skill standardizes ticket generation by validating input and applying configured templates to ensure issues include What, Why, Acceptance Criteria, story points, and activity type.

Can I create Jira bugs and tasks with enforced acceptance criteria?

Yes, you can create Jira bugs and tasks with enforced acceptance criteria. The skill supports multiple issue types including bugs and tasks, validating input and applying templates to guarantee required sections like Acceptance Criteria are populated.

Does Jira ticket generation support post-create refinement in the web UI?

Jira ticket generation does support post-create refinement in the web UI. After generating a structured issue from a natural language prompt and applying templates, you can adjust the created ticket directly within the web UI.

Why do my manually created Jira tickets have missing required fields?

Manually created Jira tickets often have missing required fields due to inconsistent structures and human error. Standardizing ticket generation with automated templates enforces best practices and ensures required sections like What, Why, and Acceptance Criteria are populated.