create-jira-item

Creates Jira stories, tasks, epics, and initiatives with automatic required custom field handling.

9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/paultyng/skill-issue --skill create-jira-item-paultyng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-jira-item
Source: https://github.com/paultyng/skill-issue/tree/main/skills/create-jira-item
Command: npx skills add https://github.com/paultyng/skill-issue --skill create-jira-item-paultyng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating Jira issues often leads to missing required custom fields, causing tickets to be rejected or delayed, especially for epics and initiatives that rely on org-specific fields like team assignment, quarter, or initiative links.

Core Features & Use Cases

  • Automatic Custom Field Introspection: Automatically discovers required custom fields and their allowed values for any project and issue type, eliminating the need to manually look up field IDs.
  • Full Issue Type Support: Creates all common Jira issue types including stories, epics, tasks, and initiatives, with correct field population for each.
  • Epic Linking & Assignee Handling: Automatically links new issues to existing epics when requested, and assigns tickets to the current user by default.
  • Use Case: For example, when creating a new epic for a Q4 product launch, this skill will automatically find and populate required fields like "Quarter" and "Initiative Link" so the ticket is accepted on the first submission.

Quick Start

Use the create-jira-item skill to make a new Jira story for the user authentication feature in the WEB project.

Frequently Asked Questions about create-jira-item

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

FAQPage Schema
How do I automate Jira ticket creation with required custom fields?

Automating Jira ticket creation requires introspecting project-specific field metadata to retrieve correct custom field IDs and allowed values. This skill automatically discovers required custom fields for stories, epics, tasks, and initiatives, ensuring tickets are accepted on the first submission without manual lookups.

How do I link a new Jira issue to an existing epic?

To link a new Jira issue to an existing epic, the skill uses epic linking functionality to automatically connect newly created stories or tasks to the specified epic. This ensures proper hierarchy and tracking within your agile project management workflow.

Can I create Jira epics and initiatives with org-specific fields like quarter and team assignment?

Yes, you can create Jira epics and initiatives with org-specific fields like quarter and team assignment. The skill automatically introspects project-specific field metadata to populate required custom fields, eliminating errors from missing or incorrectly populated values for higher-level issue types.

What is the best way to avoid Jira ticket rejection due to missing custom fields?

The best way to avoid Jira ticket rejection from missing custom fields is to automatically retrieve and populate correct custom field IDs and allowed values. By introspecting field metadata before issue creation, the skill ensures all required fields are valid for the target project and issue type.

Does this skill support assigning Jira tickets to the current user automatically?

Yes, this skill supports assigning Jira tickets to the current user automatically. When creating stories, epics, tasks, or initiatives, it handles assignee population by default, streamlining the issue tracking process and reducing manual ticket configuration steps.

How does custom field introspection work for Jira issue types?

Custom field introspection for Jira issue types works by automatically querying project-specific field metadata to discover required fields and their allowed values. This eliminates manual field ID lookups and ensures that stories, epics, tasks, and initiatives are created with valid, correctly populated custom fields.