Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mk
Bulk JIRA operations on 10+ issues: transition, assign, set-priority, clone, delete. Enforces mandatory dry-run first, then two-step user confirmation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mk:jira-bulkWhen to use
Use for any operation touching 10+ Jira issues at once. Dry-run is MANDATORY first. NOT for individual issue ops.
jira-bulkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Forks to the `jira-bulk` agent. The agent enforces a hard dry-run-first rule at runtime.
Forks to the jira-bulk agent. The agent enforces a hard dry-run-first rule at runtime.
Step 1: invocation + --dry-run
Step 2: agent shows would_* JSON keys + impacted-count
Step 3: explicit user "yes" → re-invoke without --dry-run
Skipping Step 1 is a hard violation. The agent will refuse if asked to skip the dry-run.
../../agents/jira-bulk.md../jira/references/{install-and-auth,cli-idioms,safety-framework}.md (Tier 4 enforcement lives in safety-framework.md)references/safety-checklist.md — pre-flight checklist for any bulk operation >50 issuesreferences/checkpoint-guide.md — checkpoint + resume strategy for 500+ issue opstasks/jira-workflows/<workflow-slug>.md — discovered statuses + transitions (run bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/fetch-workflow.sh <KEY> if absent; see jira-lifecycle/references/workflow-discovery.md)bulk transition --to "<Status>", validate the target status name exists in the cache; for --id <N>, validate the transition ID exists. Mismatch → reject before exec.mk:jira-search (JQL author + bulk-update overlap — same dry-run discipline), mk:jira-lifecycle (single-issue transitions; same cache), mk:jira-relationships (bulk-link is here)npx claudepluginhub ngocsangyem/meowkit --plugin mkBulk operations for multiple issues at scale. TRIGGERS: 'bulk update', 'bulk close', 'bulk transition', 'bulk assign', 'transition N issues' (N >= 10), 'update all bugs', 'close 50 issues', 'mass transition', 'update multiple issues', quantities like '50 issues', '100 bugs', '20+ tickets'. Use for operations on 10+ issues. NOT FOR: single issue transitions (use jira-lifecycle), searching only without modifications (use jira-search), single issue field updates (use jira-issue).
Bulk transitions multiple Jira issues matching a JQL filter to a target status using the jirac CLI, extracting project, filter, and options from requests.
Transitions Jira issues through workflow states, assigns users, resolves, reopens, and manages versions/components. Not for issue CRUD or bulk transitions.