The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
I have an Epic with Stories as Sub-tasks, and these Stories have sub-tasks too.
When I clone the Epic (including sub-tasks) , I expected that my Stories AND their sub-tasks would be cloned as well. But my Story sub-tasks have not be cloned. This is very dis-appointing because it blocks my use case here.
Is there a configuration that allows these recursive sub-task cloning, or is it a bug/missing feature?
2 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
It sounds like you're trying to clone an Epic that contains Stories which themselves contain sub-tasks — essentially a three-level issue hierarchy. The standard Jira cloning feature unfortunately does not support cloning a complex hierarchy like this, which can indeed be limiting for more complex project structures.
Clone an entire Epic along with all associated issues — including multiple hierarchy levels like Stories and their sub-tasks.
Preserve issue links, attachments, comments, and even issue status and custom field values.
Customize your clone using the field editor or automate the process with post functions.
This makes Deep Clone an excellent choice for replicating complex issue trees such as template Epics or entire project structures. You can even bulk clone large numbers of issues or clone whole projects if needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.