jira-create-ticket

Create Jira tickets in the MYK project with required custom fields.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mykaarma/claude-sutras --skill jira-create-ticket-mykaarma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-create-ticket
Source: https://github.com/mykaarma/claude-sutras/tree/main/skills/jira-create-ticket
Command: npx skills add https://github.com/mykaarma/claude-sutras --skill jira-create-ticket-mykaarma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes the creation of Jira issues in the MYK project by ensuring all required custom fields and structured data are collected before ticket creation, reducing errors and back-and-forth clarification.

Core Features & Use Cases

  • Guided data collection: Checklist-driven prompts to gather summary, issue type, assignee, assignee team, problem statement, requirements, and epic link when applicable.
  • Templates and field mapping: Predefined JSON templates for Task, Bug, and Story that map inputs to MYK-specific customfield IDs.
  • Validation and structured output: Validates summary clarity and assignee email domain, then calls the configured MCP Jira create action and returns a machine-readable JSON block with the ticket ID and URL.
  • Use case: Report a production bug or log a new feature request with all acceptance criteria and custom fields filled for direct consumption by engineering and product teams.

Quick Start

Create a Jira ticket in the MYK project with summary "Login fails on mobile", issue type Bug, assignee [email protected], assignee team Platform, a concise problem statement, and acceptance criteria so the skill can create the ticket and return its ID.

Frequently Asked Questions about jira-create-ticket

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

FAQPage Schema
How do I create a Jira ticket with required custom fields?

To create a Jira ticket, you must provide the summary, issue type, assignee, assignee team, problem statement, and requirements. The skill uses checklist-driven prompts to collect these mandatory fields and maps them to MYK-specific customfield IDs before invoking the MCP Jira create action.

What issue types are supported for Jira ticket creation in the MYK project?

Jira ticket creation in the MYK project supports Task, Bug, and Story issue types. Predefined JSON templates are used to map your provided inputs and custom fields to the correct MYK-specific customfield IDs for each respective issue type.

Can I use MCP to automate Jira issue tracking and standardize data collection?

Yes, you can use this MCP-based skill to automate Jira issue tracking by standardizing data collection. It validates summary clarity and assignee email domain before creating the ticket, ensuring all required custom fields are collected to reduce back-and-forth clarification errors.

What information do I need before creating a Jira bug or story?

Before creating a Jira bug or story, you need a clear summary, the issue type, the assignee's email address, the assignee team, a concise problem statement, and the specific requirements or acceptance criteria. An epic link is also required when applicable to the ticket.

Does Jira ticket creation validate the assignee email domain?

Yes, Jira ticket creation validates the assignee email domain to ensure correctness before submission. The skill checks the summary clarity and assignee domain format, then returns a structured JSON block containing the ticket ID, URL, summary, and status after the issue is successfully created.