duplicate-epic

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.

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.

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.

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.

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.

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.