batch

Execute mixed Jira create, update, transition, and archive operations from a JSON manifest.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of doing many different Jira changes one by one, which is slow and error-prone when you need to create, update, transition, and archive issues together.

Core Features & Use Cases

  • Mixed batch operations: Create, update, transition, and archive issues from a single manifest.
  • Manifest-driven workflow: Express each operation as a JSON object with an op field, then execute them together.
  • Bulk orchestration use case: When you have a list of issues that need different end states (e.g., new tickets created while older ones are updated and moved to Done), you can manage the whole rollout in one run.

Quick Start

Provide a JSON manifest with create, update, transition, and archive operations, save it as a file, then run a single batch command to execute all operations and return a per-operation summary.

Frequently Asked Questions about batch

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

FAQPage Schema
How do I run mixed Jira create, update, and transition operations in one batch?

Mixed Jira batch operations are executed from a JSON manifest where each object contains an op field and required attributes for its specific action. You save this manifest as a temporary file and run a single batch command to process all operations together with per-op result reporting.

What is the best way to bulk update and transition multiple Jira issues to different end states?

Bulk updating and transitioning Jira issues to different end states is handled by a manifest-driven workflow. You define each issue's desired action and target state in a JSON manifest, then execute one command to orchestrate the entire rollout across all specified issues.

How do I structure a JSON manifest for Jira bulk issue transitions and updates?

A JSON manifest for Jira bulk operations requires each operation expressed as a JSON object with an op field designating the action type, alongside required attributes specific to that operation. The manifest is saved to a file before execution.

Do I need jirac installed to perform automated batch issue transitions from a manifest?

Yes, jirac availability is required to execute manifest-driven Jira batch operations. The Skill relies on jirac to process the JSON manifest and perform the coordinated create, update, transition, and archive actions.

Can I create new Jira tickets and archive older ones in the same automated workflow run?

Yes, creating new tickets while archiving older ones in the same run is the core use case for mixed batch operations. You specify creation and archive operations as separate entries within the same JSON manifest to manage the full rollout in one execution.

How do I verify the results of a bulk Jira update after running a batch operation?

Verifying bulk Jira update results is handled by per-op result reporting returned after the batch command executes. The execution output provides a summary indicating the outcome of each individual operation processed from the manifest.