---
title: "Clone an initiative and its issues"
canonical: "https://support.appfire.com/space/JCPP/1853719217/Clone%20an%20initiative%20and%20its%20issues"
format: markdown
---
> Macro (aura-html)

This page details how to clone an initiative and its issues. You can clone an initiative, including its epics,  tasks, subtasks, and so on.

> Macro (iframe)

This use case is to clone the initiative issue type, one level above the epic issue type in the issue type hierarchy. However, in Jira premium, you clone higher levels, such as goal, theme, feature, capability, and other issue types in the issue type hierarchy.

![Screenshot of the Issues type hierarchy page.](media://5751371c-f72a-42e8-bc0d-4384402ddc85)

# Steps

1. Select an initiative you want to clone in your Jira instance. For example, consider an initiative, including its epics, tasks, and subtasks, as shown in the following image.
2. In the top-right corner, select **Actions ** > **Clone Plus*** *option or the **Clone Plus** quick-add button for any issue.
3. On the *Clone Plus for Jira *page, do the following:
  1. In the **Clone operation** field, select the clone operation you want to apply to the cloned issues.
  2. In the **Project** field, select the project to which you want to clone the issues.
  3. In the* ***Issue type** field, select the **Initiative*** *issue type.
  4. In the **Clone options** section, click the **Subtasks** clone option.
4. Click **Clone**.
5. On the *Create issue *page, select values for all the issue fields as required.
6. Click **Create**.  
Jira displays a successful issue creation message, and the initiative, including its epics, tasks, and subtasks, is now cloned to a new initiative.

> ℹ️ - Currently, when you clone an initiative to another issue type from a **different level **of the issue type hierarchy (epic, capability, and so on), **the child issues cannot be cloned**.
> ℹ️ - When you clone an issue tree, ensure all **the issue types exist in the target project**. If the issue type does not exist in the target project, the issue will not be cloned.
> ℹ️ - When you clone an initiative with its child issues from a different project, the entire issue tree will be cloned to the project selected on the *Clone Plus for Jira*** **page, that is:
> ℹ️   - If you select the **Same Project** option, all the issues in the issue tree will be cloned to **the same project as the original issue**.
> ℹ️   - If you select the specific target project, all the issues in the issue tree will be cloned to **the selected target project**.