skills.rest
mulhamna
mulhamnaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clone-issue

Clones a Jira issue into a new project with optional summary and assignee overrides.

46|12|Updated Apr 15, 2026
Search Tags:#jira#project migration#issue key#issue cloning#ticket duplication#assignee assignment#move issue
One-click install
npx skills add https://github.com/mulhamna/jira-commands --skill clone-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clone-issue
Source: https://github.com/mulhamna/jira-commands/tree/main/plugin/skills/clone-issue
Command: npx skills add https://github.com/mulhamna/jira-commands --skill clone-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cloning Jira issues without losing important fields forces teams to repeat manual setup and risk inconsistencies between source and target issues.

Core Features & Use Cases

  • Field-preserving cloning: Copies summary, description, type, priority, labels, components, and fix versions so the clone stays aligned with the original.
  • Target customization: Optionally changes the destination project and overrides the summary for the clone.
  • Controlled assignment and optional move: Lets you set an assignee on the clone (without copying the source assignee by default) and can delete the original issue using move semantics.

Quick Start

Ask to clone issue PROJ-123 into project NEWPROJ with a new summary and assigned user, and the system will create the cloned issue and confirm the new key.

Frequently Asked Questions about clone-issue

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

FAQPage Schema
How do I clone a Jira issue to another project without losing key fields?▼

Cloning a Jira issue creates a new ticket that preserves summary, description, type, priority, labels, components, and fix versions from the source, while allowing targeted changes to the destination project and assignee.

Can I move a Jira ticket to a different project and delete the original issue?▼

Yes, you can move a Jira ticket by applying move semantics during the issue cloning process, which creates the duplicated ticket in the new project and deletes the original issue automatically.

What Jira fields are copied when duplicating a ticket for a new workstream?▼

Duplicating a ticket copies the summary, description, issue type, priority, labels, components, and fix versions to ensure the clone stays aligned with the original source issue without manual re-entry.

How do I assign a cloned Jira issue to a different user during ticket duplication?▼

During ticket duplication, you can set a specific assignee on the cloned Jira issue through an optional override, which prevents copying the source assignee by default and directly assigns the new ticket.

Do I need a specific tool installed to automate Jira issue cloning via command line?▼

Yes, you must ensure the jirac command line tool is available in your environment, as the system relies on it to parse source keys, execute the issue clone operation with the correct flags, and confirm the resulting key.

Related Skills

Explore More Product & Management Skills→
missdeermissdeer

jira

Manage JIRA Server and Data Center issues via REST API v2.

Community
Intermediate
0xMerl990xMerl99
1

jira

Manage Jira issues, sprints, workflows, and JQL reporting.

Community
Intermediate
mulhamnamulhamna
46

bulk-create

Create multiple Jira issues from a JSON manifest file.

Community
Intermediate
mulhamnamulhamna
46

Change a Jira issue to another issue type using Jira's native move semantics with jirac

Change a Jira issue type while preserving its key using jirac CLI.

Community
Intermediate