jira-bulk_skill

Overview

This skill performs bulk operations on 10+ JIRA issues at scale, including transitions, assignments, priority changes, cloning and permanent deletion. It is designed for safe, auditable mass changes with dry-run previews, progress tracking, and failure summaries. Use it when you need to modify many issues at once rather than handling single-issue edits.

How this skill works

Commands accept either JQL or explicit issue keys and run changes in batches. Every command supports --dry-run to preview actions, --max-issues to limit batch size, and output options for scripting. Safety checks include confirmation prompts for large sets, per-issue error reporting, and exit codes that indicate full success, partial failures, or cancellation.

When to use it

• When you need to transition 10 or more issues through workflow states
• When assigning many issues to a user or unassigning at scale
• When setting priority across a large set of bugs or tasks
• When cloning many issues with subtasks and links (preview first)
• When permanently deleting many issues and you need a safe preview

Best practices

• Always run with --dry-run first for any operation affecting >10 issues
• Use --max-issues to process large sets in controlled batches (recommended for 500+)
• Run destructive actions like bulk delete only after reviewing dry-run output and confirming permissions
• Prefer scheduled runs or off-peak hours to reduce rate limit errors
• Use -o json for machine-readable output and -y/--yes only in tested automation scripts

Example use cases

• Transition all In Progress issues in a sprint to Done using a JQL query and --dry-run to preview
• Assign all open issues for a component to a new owner after a team change
• Set priority High for all bugs labeled critical across projects
• Clone an entire sprint into a new project with subtasks and links after reviewing the dry-run
• Permanently delete a cleanup project’s issues after confirming the dry-run and required permissions