create-jira-item

Create Jira work items with defaults via Atlassian MCP.

4|Updated Apr 10, 2023
One-click install
npx skills add https://github.com/dudeofawesome/nix-config --skill create-jira-item
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-jira-item
Source: https://github.com/dudeofawesome/nix-config/tree/main/modules/presets/home-manager/paciolan/llms/skills/create-jira-item
Command: npx skills add https://github.com/dudeofawesome/nix-config --skill create-jira-item

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating Jira work items with correct defaults is time-consuming and error-prone. This skill automates setup to ensure consistency across projects.

Core Features & Use Cases

  • Load defaults, workflow transitions, and field mappings from jira-defaults to pre-populate items.
  • Determine the issue type automatically (default to Story) or infer from context.
  • Derive the title from ARGUMENTS or provide three suggested options based on the current repo, applying the project label when available.
  • Create the work item via Atlassian MCP and transition it to the target status while reporting key details.

Quick Start

Run /create-jira-item with an optional title to create a Jira work item using the configured defaults.

Frequently Asked Questions about create-jira-item

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

FAQPage Schema
How do I auto-generate Jira tickets with sensible defaults from my repository?

You can auto-generate ready-to-create Jira tickets by loading sensible defaults from jira-defaults, auto-detecting repo context, and mapping top-level projects to pre-populate parent, assignee, and labels.

What's the best way to create Jira work items across multiple projects consistently?

The best way to create consistent Jira work items across multiple projects is to load workflow transitions and field mappings from jira-defaults, determine the issue type automatically, and apply configured project labels.

Can I use package.json to derive the repo name label when creating a Jira story?

Yes, you can read package.json to derive the repo name label. The system reads the file to apply the project label automatically when generating title options or creating the Jira story.

How do I transition a newly created Jira task to a target status automatically?

To transition a newly created Jira task to a target status automatically, the system creates the work item via Atlassian MCP and immediately applies the configured workflow transition before reporting the issue key and URL.

Does this Jira ticket automation tool suggest titles if I don't provide one?

Yes, if you do not provide a title via ARGUMENTS, the automation suggests three title options based on the current repository context and applies the relevant project label before creating the Jira work item.

What details are reported back after creating a Jira work item via Atlassian MCP?

After creating a Jira work item via Atlassian MCP, the system reports the issue key, URL, summary, and current status to confirm the ticket was successfully generated and transitioned to the target state.