Jira Create Ticket

If the user hasn't provided all required fields, ask for the missing ones before creating.

Workflow

1. Gather Information

Ask the user for missing details. Use conversational prompts:

• "What type of issue is this? (Task, Bug, Story)"
• "Which team should this be assigned to?"
• "Does this involve any UI/UX changes?"
• "Can you describe the problem / current state?"
• "What are the requirements or acceptance criteria?"

2. Validate

• Confirm the summary is clear and descriptive
• Ensure issue type matches the work (Bug for defects, Story for features, Task for work items)
• Verify the assignee email is valid (@mykaarma.com)

3. Create the Ticket

Use mcp__jira__jira_create_issue with the appropriate template below.

4. Confirm

• Show the created ticket key (MYK-XXXXX) and link
• Summarize what was created

MYK Custom Fields Reference

Templates

Task

{
  "project_key": "MYK",
  "summary": "<clear title>",
  "issue_type": "Task",
  "assignee": "<user>@mykaarma.com",
  "additional_fields": {
    "customfield_11996": {"value": "<team>"},
    "customfield_12018": {"value": "No"},
    "customfield_12012": "<problem statement>",
    "customfield_12025": "<requirements>",
    "customfield_10105": "<epic-key if applicable>"
  }
}

Bug

{
  "project_key": "MYK",
  "summary": "[Bug] <clear description of defect>",
  "issue_type": "Bug",
  "assignee": "<user>@mykaarma.com",
  "additional_fields": {
    "customfield_11996": {"value": "<team>"},
    "customfield_12018": {"value": "No"},
    "customfield_12012": "Current behavior: <what happens>\nExpected behavior: <what should happen>\nSteps to reproduce:\n1. <step>\n2. <step>",
    "customfield_12025": "1. <fix requirement>\n2. <verification criteria>",
    "customfield_10105": "<epic-key if applicable>"
  }
}

Story

{
  "project_key": "MYK",
  "summary": "<user-facing feature title>",
  "issue_type": "Story",
  "assignee": "<user>@mykaarma.com",
  "additional_fields": {
    "customfield_11996": {"value": "<team>"},
    "customfield_12018": {"value": "<Yes/No>"},
    "customfield_12012": "As a <role>, I need <capability> because <reason>.\n\nCurrent state: <description>",
    "customfield_12025": "Acceptance criteria:\n- [ ] <criterion 1>\n- [ ] <criterion 2>\n- [ ] <criterion 3>",
    "customfield_10105": "<epic-key if applicable>"
  }
}

Field Format Quick Reference

• Dropdown/Radio fields: {"value": "option_name"}
• Text/Textarea fields: "text content directly"
• Multi-select fields: [{"value": "option1"}, {"value": "option2"}]
• User fields: "[email protected]" or display name or account ID

Structured Output

After creating the ticket, emit a JSON block so downstream automation (MCP tools, other skills) can capture the ticket ID without parsing prose.

{
  "ticket_id": "MYK-XXXX",
  "url": "https://mykaarma.atlassian.net/browse/MYK-XXXX",
  "summary": "The ticket summary text",
  "status": "created"
}

• ticket_id — the Jira issue key returned by the API (e.g. MYK-4821)
• url — direct browser link constructed from the key
• summary — the summary field sent to Jira, for confirmation
• status — always "created" on success; emit "failed" with an "error" field if the API call errors

This block should appear as the last fenced code block in the response so consumers can reliably find it. See skills/structured-output/SKILL.md for the standard envelope format.