I would like to create a set of Epics and Tasks that I can reuse for future business efforts.

unknown

I need to map out and create a process that will be repeated each time we deploy this solution to a new client or site.   I have created a repeatable business effort as a (Version) with an organized group of (Epics) containing (Stories).  Is this a good method or is there a more efficient way?  Should this be a Jira (Template)?   Looking for the optimal steps for setting up these unique efforts and then copying them into a New Unique Epic/Story/Task so that they are not all linked.   (truly unique)

Reading through some of the comments it appears that Deep Cloning the Epics and Tasks might be the right path... I just don't want the connection between the cloned story / epic.  

Do I need to create a new (Version) and then Deep Clone the Epic with Stories ... Is there an option to toggle and uncouple? ... so that I create new and unique stories and epics for each repeated business effort?

Petter Gonçalves

Hello @[deleted]

Welcome to the Atlassian Community!

Per your description, I understand that you would like to automatically create a pre-determined set of issues (Epics and Stories not having any links between them) with a default template for each client you have, at the time that is more convenient to you. Is that correct?

If I understood it properly, I believe the inbuilt Jira Automation would be the best solution to achieve your need. Using this feature, you can automatically create issues with pre-determined fields, triggering the event by a specific action in Jira Site. E.g: Version created.

Let me give you a practical example so we can confirm we are on the same page here:

Let's suppose you want the set of issues to be created for a project/client every time you create a new Version in your Project. These would be the steps to achieve it:

1. Navigate to your Project > Project settings > Automation
2. Click to "Create rule", adding the following structure, adding as many issues as you need with the fields you want to be filled:
   
   

A few observations:

1. You can pre-set the values of any fields you want in the issues, optionally changing it after the creation
2. Jira automation does not fully support Next-gen projects yet, so we suggest using it on Jira Classic projects
3. Automation rules can be configured on a Project basis or as Global (Appling to all the projects in your site), however, The number of executions are month-limited for Global rules

You can check more details about Jira Automation in the link below:

Jira Cloud Automation 

Let us know if you have any questions.