You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
For process specific stories, using Epics with template stories is a great approach. How can such Epics be cloned along with the stories?
There are Marketplace apps you can add to your Jira that will do "deep clone" operations like this. You can try most of them out for free to see how they work, and/or explore the documentation for each app to find one that matches your needs (and price point). Here's one that we use.
Alternately, you can do a bit of "roll your own solution" with Jira Automation. You could define an automation rule that you can manually execute on an Epic, and it can clone that Epic and then iterate through the child Stories and clone each of them, putting them under the Epic.
For both of these solutions I'd suggest searching the Atlassian Community here for more info. Others will have discussed both apps that clone as well as automation for deep cloning.
Hi @Sduvvuri and welcome to the community!
I'm Luka from codefortynine 👋
As @Mykenna Cepek already mentioned, there are solutions for your use case in the Marketplace.
Our app Deep Clone for Jira allows you to clone Epics and all their linked issues with its Epic/Tree Clone feature, including Stories. This ensures that the structure and relationships between your Epic and its Stories are preserved in the clone.
Should you encounter any issues or have further questions, feel free to reach out.