Selecting tasks from a epic to clone

[kmurphy]

We have epic templates that have a handful of tasks. Each epic is for a different type of campaign. However, there are instances when some tasks aren't needed. Is there a way to essentially pick form a check list of existing tasks to clone over to a new epic? IE..

We have Epic A with 15 tasks for a campaign type. The next time we are running a similar campaign type, I would like to be able to check that we need 7 of those tasks in our new Epic B. Right now, we clone the entire Epic A and delete or close out tickets that aren't needed for Epic B.

[JM Perrot · Accepted solution]

You can export your Epic and issues in CSV format, then re-import that CSV. When importing, don't map any fields you don't want to copy, such as the issue key or creation date.
You can also take an add-on to do that but there is no native feature in Jira to do that at my knowledge.

[kmurphy]

It's less about the fields within the tickets and more the tickets themselves if that makes sense

[Luka Hummel - codefortynine · Accepted solution]

Hi @kmurphy

I'm Luka from codefortynine, and our app Deep Clone for Jira might be useful to you. It is quite powerful when used to clone Epic templates. You can also de-select unneeded issues before cloning.

Let me know if this is what you were looking for.

[kmurphy]

Thank you so much, this is exactly what I was hoping for!