bulk-create

Create multiple Jira issues from a JSON manifest file.

46|12|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mulhamna/jira-commands --skill bulk-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bulk-create
Source: https://github.com/mulhamna/jira-commands/tree/main/plugin/skills/bulk-create
Command: npx skills add https://github.com/mulhamna/jira-commands --skill bulk-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a long list of Jira items into individual issues is slow and error-prone when done manually, especially when you need consistent fields, labels, and descriptions across many tickets.

Core Features & Use Cases

  • Bulk issue creation from a manifest: Create multiple issues at once by defining an array of issue objects in a JSON file (project and summary required).
  • Supports common Jira fields in one pass: Set issue type (defaulting to Task), assignee (including “me”), priority, labels, components, parent links, fix versions, and custom fields.
  • Markdown-ready descriptions: Provide each issue’s description as a Markdown string and publish it during creation.

Quick Start

Ask the assistant to build your issues.json manifest for your project and then run jirac issue bulk-create with that manifest to create the tickets.

Frequently Asked Questions about bulk-create

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

FAQPage Schema
How do I create multiple Jira issues at once from a JSON file?

You can create many Jira issues from a JSON file by defining an array of issue objects with required project and summary fields, then executing the jirac issue bulk-create command with the provided manifest file path to generate the tickets.

Can I set custom fields and assignees when bulk creating Jira tickets?

When bulk creating Jira tickets, you can set custom fields, assignees including me, priority, labels, components, parent links, and fix versions in a single pass by defining them within each issue object in your JSON manifest.

What is the best way to seed a Jira backlog with consistent issue schemas?

Seeding a Jira backlog with consistent schemas is best done using a JSON manifest for bulk issue creation, allowing each ticket to share a uniform structure while varying fields like labels and assignees without repetitive manual entry.

Does bulk Jira issue creation support Markdown for ticket descriptions?

Bulk Jira issue creation supports Markdown for ticket descriptions. You provide each issue's description as a Markdown string in the JSON manifest, and it publishes the formatted text during the creation process.

What are the required fields for a Jira bulk create JSON manifest?

The required fields for a Jira bulk create JSON manifest are project and summary for each issue object. Other fields like issue type default to Task if not specified, while assignees and custom fields remain optional additions.