From jira
Creates Jira tickets interactively: prompts for project, type, summary, description, priority, assignee, labels; confirms before Atlassian API creation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira:createThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
jira:create - Create a new Jira ticket interactively
jira:create - Create a new Jira ticket interactively
/create [arguments]
Create a new Jira ticket interactively
Create a new Jira ticket through an interactive prompt.
Usage: /create [optional: initial summary]
Interactive Prompts:
Project (if not obvious from context)
atlassian_search_issues to list available projectsIssue Type
Summary (required)
Description (optional)
Priority (optional, default: Medium)
Assignee (optional)
Labels (optional)
Confirmation: Show summary and ask for confirmation before creating:
📝 Create New Ticket
Project: PROJ
Type: Story
Summary: {summary}
Description: {description preview}
Priority: High
Assignee: You
Labels: {labels}
Create this ticket? (y/n)
After creation, use atlassian_create_issue and display:
✅ Created PROJ-123: {summary}
Link: {ticket URL}
What would you like to do next?
- Start work (/start PROJ-123)
- View details (/ticket PROJ-123)
npx claudepluginhub thebushidocollective/han --plugin jiraCreates new Jira issues using jirac CLI, extracting project key, issue type, summary, assignee, labels, priority, and custom fields from requests with interactive prompts.
Creates Jira issues via CLI flags or work-item files. Converts Markdown body to ADF, previews payload, requires confirmation, then POSTs to Jira.
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).