Can I clone a Template with all the issues in Next Gen?

[Debi.Damas]

I am trying to use Jira to create implementation Epics for each customer with the same steps in the process.  I created a template customer and tried to clone it.  While the name saved, none of the issues were cloned despite my choosing to clone attachment, which is really not the same as issues.  I still have to add all the issues.  

This to me should be something that I should be able to do if the process is repeatable.  

Am I wrong?

[Marlene Kegel - codefortynine · Accepted solution]

Hi @Debi.Damas ,

If @Jack Brickey 's suggestion doesn't work for you, you could also try our app Deep Clone for Jira.

With our app you can clone Epics with all included tasks.

Don't hesitate to get in touch with our support if you have questions or feedback.

[Debi.Damas]

Thank you, Marlene.  I would think this is something that would be included with the product and not an additional cost.  I will take this back to my org to see if this is the direction we want to move.  

[Jack Brickey]

yep have heard good things about the addon but have not had the opportunity to use myself.

[Marlene Kegel - codefortynine]

You're welcome, Debi!

I hope you'll have the opportunity some day, @Jack Brickey :)

[Jack Brickey · Accepted solution]

Disclaimer: I don't use NG much and certainly not for this specific suggestion. While I know it will work for Classic I'm unsure if there are any NG - automation limitations that would preclude the solution or not.

I would recommend you use Automation to create this 'template' and run it when you want. Specifically I would suggest doing so as follows...

Trigger - issue created

Condition - JQL issuetype = Epic

Condition - JQL some other unique thing e.g. labels = new-client-template

Action - create issues to meet your needs

when you want to create another one of the epic trees simply create the Epic and set the condition to ensure the automation succeeds, e.g. my suggestion for label. The reason I suggest this unique condition is so that you don't create the tree for every epic you might create in the project.

[Debi.Damas]

Thanks for your help.  This seems like a lot of work to do for something that IMO should already be there. 

[Jack Brickey]

Don't really disagree. Having a 'clone epic and all associated issues' would be nice. You might be interested in this open suggestion (JSWCLOUD-7721) where you can vote/watch and comment. It is a very old suggestion though. :-(

[Debi.Damas]

There are many things that I think should be there that have been old suggestions.  Hmmm.  Makes me wonder if there are product managers looking at the requests or sales/upper management wanting to make cool stuff over functional stuff. 

[Jack Brickey]

i can't really weigh in on that TBH as I am but a user like yourself. However, I can say that I am frequently engaged w/ a number of PMs on product feedback sessions so my experience/opinion is they are listening. But I certainly understand/empathize with your feelings. :-( 

[Debi.Damas]

Thanks, all!  I appreciate your feedback!

[Marlene Kegel - codefortynine]

You're welcome, @Debi.Damas !