Can I set assignees and labels using this skill?

Yes, the skill allows you to specify assignees (using email or account IDs), priority levels, labels, components, and even Epic links.

What kind of JIRA issues can I create?

The skill supports creating Stories, Bugs, Tasks, and Epics, providing a specialized markdown template for each type.

What authentication is needed?

You need an Atlassian API token and your Jira site URL to authenticate either the MCP server or the CLI.

How does the skill handle complex ticket descriptions?

It builds descriptions using structured markdown templates and, when using the CLI, utilizes description files to ensure multi-line formatting is preserved perfectly.

Does this skill require the Atlassian CLI to be installed?

No, it prefers the Atlassian MCP Server for direct API integration. The CLI (acli) is only used as a fallback if the MCP server is not available.

Jira Issue Creator

Name: Jira Issue Creator
Author: bcowdery

bybcowdery

Collaboration Tools

Automates the creation of well-structured JIRA tickets using standardized templates and direct API or CLI integration.

About

The Jira Create skill streamlines project management by helping developers and product owners generate high-quality JIRA issues directly within their workflow. By guiding users through interactive prompts and applying pre-defined templates for Stories, Bugs, and Tasks, it ensures all necessary information—like acceptance criteria using RFC 2119 language and reproduction steps—is captured accurately. Whether using the Atlassian MCP Server for direct API access or the Atlassian CLI for local environments, this skill maintains organizational standards while reducing the friction of manual ticket creation.

Key Features

Enforces RFC 2119 terminology (MUST, SHOULD, MAY) for clear requirements
Interactive prompts for gathering project keys, labels, and assignees
Supports Atlassian MCP Server for direct, authenticated API integration
Provides CLI fallback support via acli for flexible environment usage
Standardized templates for Stories, Bugs, Tasks, and Epics
0 GitHub stars

Use Cases

Filing detailed bug reports with reproduction steps and environment details during debugging
Drafting user stories with clear acceptance criteria and technical context for sprint planning
Converting development tasks identified during code reviews into trackable JIRA issues

About

Key Features

Enforces RFC 2119 terminology (MUST, SHOULD, MAY) for clear requirements
Interactive prompts for gathering project keys, labels, and assignees
Supports Atlassian MCP Server for direct, authenticated API integration
Provides CLI fallback support via acli for flexible environment usage
Standardized templates for Stories, Bugs, Tasks, and Epics
0 GitHub stars

Use Cases

Filing detailed bug reports with reproduction steps and environment details during debugging
Drafting user stories with clear acceptance criteria and technical context for sprint planning
Converting development tasks identified during code reviews into trackable JIRA issues