duplicate-epic

Name: duplicate-epic
Availability: InStock
Author: PatternFly

Clone Jira epics into PatternFly Jira and link duplicates via REST API.

10|26|Updated Jul 8, 2025

Search Tags:#automation #jira #epic #clone #project-management #issue-link #atlassian-api

Ready to run

npx skills add https://github.com/patternfly/ai-helpers --skill duplicate-epic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: duplicate-epic
Source: https://github.com/patternfly/ai-helpers/tree/main/plugins/issue-management/skills/duplicate-epic
Command: npx skills add https://github.com/patternfly/ai-helpers --skill duplicate-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

Cloning Jira epics between spaces is a manual, error-prone process that can break traceability. This Skill automates the clone-and-link workflow, ensuring consistency between source and PF space while preserving important attributes.

Core Features & Use Cases

Clone a Jira Epic from a source project into the PF space, carrying over the summary and labels.
Create a PF Epic clone and automatically link it to the original Epic via a Duplicate relationship, then assign it to the specified PF feature.
If a non-Epic input is provided (e.g., a Story or Bug), resolve to its parent Epic to maintain correct hierarchy before cloning.

Quick Start

Run the script with the source issue key and the PF feature key to clone and link the epic.

Frequently Asked Questions about duplicate-epic

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

FAQPage Schema

How do I clone a Jira epic to another project and link the duplicate?▼

To clone a Jira epic to another project and link the duplicate, this Skill uses the Jira REST API to create a new epic in the target space, preserves the summary and labels, assigns it to a feature, and establishes a duplicate issue link to the source epic.

Can I clone a Jira epic if I only have the Story or Bug issue key?▼

Yes, you can clone a Jira epic with only a Story or Bug key. The script automatically resolves non-epic inputs to their parent epic before cloning, ensuring the correct hierarchy is maintained across the source and target projects.

What Jira credentials do I need to automate epic cloning via the REST API?▼

Automating epic cloning via the Jira REST API requires setting Jira credentials as environment variables. The script uses curl and jq to call the myself, issue, and issueLink endpoints for authentication, cloning, and linking.

How does the duplicate epic linking process preserve Jira traceability?▼

The duplicate epic linking process preserves Jira traceability by creating a duplicate relationship between the newly cloned epic and the original source epic. This ensures a clear connection is maintained across different project spaces.

What is the best way to automate cloning Jira epics across multiple project spaces?▼

The best way to automate cloning Jira epics across project spaces is using a script that leverages the Jira REST API to copy summaries and labels, assign parent features, and automatically resolve parent epics from nested issues.

Are there limitations when cloning Jira epics with this automation script?▼

A limitation when cloning Jira epics is that the script only preserves the summary and labels, meaning other custom fields, descriptions, or attachments from the source epic are not transferred to the new clone.