nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to clone the whole Epic and child issues included in the Epic

Lin Zhang_q23u4x

Hi Team,

How to clone the whole Epic and child issues included in the Epic?

Curently I‘’m using the free version of Jira, so I would like to know that do we have this function? How to use it?

Much apperaciate if you can help with this questions, thanks.

Best regards,

Summer

Accepted answers

Peter Youngman

Hi @Lin Zhang

Create an automation rule like this - note that the right-hand part shows what you need to enter for the "create variable"-step (highlighted in dark background within the logic of the rule. Copy Epic including Stories within it.png

And what you need to set in the last "create"-step...

Copy Epic including Stories within it2.png

John Funk

Hi Lin - Welcome to the Atlassian Community!

We use an add-on called Deep Clone that will clone the Epic and all of the children. Otherwise out of the box Jira will not provide that.

All comments

Fernando Eugênio da Silva

Hey, @Lin Zhang

I'm not sure if natively in the free version this feature is available.

I also tried to do this in a free cloud version even by automation, but I wasn't completely successful.

In the Standard version this option is completely released.

What you can try using the Standar version of the Cloud is to install the Script Runner plugin for the Cloud version, it is free for up to 10 users. In it you can work with some script that makes this cloning of epics with their child issues

Peter Youngman

Hi @Lin Zhang

And what you need to set in the last "create"-step...

Copy Epic including Stories within it2.png

John Funk

Hi Lin - Welcome to the Atlassian Community!

We use an add-on called Deep Clone that will clone the Epic and all of the children. Otherwise out of the box Jira will not provide that.

Lin Zhang_q23u4x

Thanks John. Is that possible to get more guidance on the function?

Lin Zhang_q23u4x

Thanks Peter. Are you using the standad version? I can't find "create variable" on my right-hand part.

Lin Zhang_q23u4x

Got it, thanks. Does it works for Kanban Board of Standard version?

Peter Youngman

We are on Jira Software cloud premium. I believe that if you can create automation rules, then the create-variable should be available. This was added to automation rules a while ago.

Marlene Kegel - codefortynine

Hi @Lin Zhang,

I am Marlene from codefortynine and the product manager of Deep Clone for Jira.

As @John Funk mentioned, it is possible to clone Epics and child issues included in the Epic.

After you've installed Deep Clone you would just have to

Navigate to the Epic you want to clone
Select Deep Clone > Epic Clone from the issue action menu
Configure your clone

Deep Clone is easy to use and designed for every Jira user.

You can read more about the Deep Clone Epic Clone in our documentation, or watch the Epic Clone demo video.

Feel free to reach out to our support, if you have further questions or feedback.

John Funk

Hi @Lin Zhang - Any update here? If this answered your question, can you click on the Accept Answer button above to close this one out? Thanks!

PATRICIA MURPHY_hyu3ak

@Peter Youngman

I tried to set up the automation you share but it is not copying the epic. It does create copies of the child stories in the epic but the child stories have no sub-tasks copied from the original stories.

I think I am missing something :-/

Any guidance you can provide is greatly appreciated Thanks automation to copy an epic and all of its child stoies and their subtasks.jpg

Laura Franceschini_jq5qnq

@Peter Youngman

I did pretty much what you have shown, above, only:

using a JQL - as I would like to clone only the "open" Epics and their "open" child (!= Done)
copying to another Jira project

w3 main issues though:

it does not copy the issue status (they are all in Backlog for some reasons)
in the JQL i selected only the Epic (AND EpicLink IN (BL-123, BL234, BL-789...). Should I use ParentEpic instead?
it does not clone and copy over only the != Done tickets

Many thanks!

Laura

Mauricio Heberle_x42e0d

Show us your rule

Laura Franceschini_jq5qnq

Here it is. It's a manual, so When manually triggered.

Thanks,

maurício heberle

From what I can understand by the ss, I'd suggest:

- Change de JQL condition from the first part. Add " Issuetype = epic and statuscategory!= Done

You are triggering the epic which is the father.

Below the branch "For stories( or other issues in epic)

- Add JQL condition " Issuetype != epic and statuscategory!= Done

- Then Clone to desired project. Fill the EpicLink field with the var you've just created

- Add transition to the status of destination workflow

Derick_36eyz2

In my case, tasks are being cloned but I can't link them to a parent, they are left loose in the project. I can't put in the Epic link as EpicKey because this is not an intelligent field, the same thing in the parent field. Both fields ask to select predefined values and do not accept a JQL. What would be the alternative in this situation?

Sergey vc

Just start type in the field. I didn't see any restrictions

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

atl-gruland

automation