Skills
.Work. You
Rest

Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)

Community

Move Jira issues without losing history

Product & Management#jira#custom fields#cross-project#worklogs#issue move#preserve history#issue key rekeying
Authormulhamna
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This skill helps you move a Jira issue to a different project while preserving its history, comments, attachments, and worklogs instead of creating a new key via clone-and-delete.

Core Features & Use Cases

  • Native issue move: Moves an issue across projects using Jira’s native move semantics so the issue history and associated content are retained.
  • Type-aware destination handling: Supports specifying the destination issue type when the target project’s type differs from the source.
  • Risk-aware confirmation: Ensures you understand that moves can drop incompatible custom-field values and reassign workflow.

Quick Start

Use jirac to move issue PROJ-123 to project OTHER and set the destination type as Task: jirac issue move PROJ-123 OTHER --issue-type Task.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)
Download link: https://github.com/mulhamna/jira-commands/archive/main.zip#move-a-jira-issue-to-another-project-using-jira-s-native-move-semantics-with-jirac-not-clone-delete

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.