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?
Hello @Michael Welch
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:
A few observations:
You can check more details about Jira Automation in the link below:
Let us know if you have any questions.
Hi @Michael Welch ,
I am happy to read that you consider Deep Clone for Jira.
I am not 100% sure if I understand your use case correctly. But there are several possibilities to configure links in your clone, as you can see in the screenshot I attached below. You are free to decide whether you want to clone issues links or not. It's also possible to remove the "clone" link between the clone and the original issue.
Per default Deep Clone maintains the structure of the original issues when you clone them in bulk. So if the template issues are not linked, neither the clones won't be linked.
Don't hesitate to get in touch with us, if you have further questions about our app. I am sure that Deep Clone is able to facilitate your use case.
You can also test the full version of Deep Clone for free to validate if your use case is possible.
I currently use deep clone but end up having to manually edit 100s of stories and so many Epics, this is not feasible. I am trying Easy Templates, but the templates only create 1 level , for instance the Initiative I use to create the template does not automatically grab all the Epics and stories within it.
i need to be able to create templates from Intiatives with Epics and stories within. so that I can then create initiatives from those template for future repeatable projects please.
Welcome to the community, @Alison Hunt.
I am sorry to hear that you have to manually edit stories when cloning.
In some cases it is not possible to clone immediately, because of e.g. missing required fields. Usually that can be fixed.
We would be happy if you contact us directly. I am sure we can help you speed up your cloning process.
Update: We investigated the issue and noticed that it was connected to another app, not Deep Clone.
Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their Jira Cloud instance. ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events