How to Clone Children Hierarchy When Portfolio Epic is Cloned in JIRA Cloud?

Question

Hi Community,

I have portfolio hierarchy i.e. Portfolio Epic > Feature > Task > Subtask in a project.

My use-case is:

* When Portfolio Epic is cloned, the linked Child (Feature) also gets cloned by default jira clone process.
* However, the grand child (Task) and great grand child (subtask) linked to the same Portfolio Epic, are not getting cloned wrt above process.

Please kindly assist on how we can clone the whole Children hierarchy when the Portfolio Epic is cloned in Jira Cloud and how it can be achieved via jira automation rules, scriptrunner behavior, or jmwe app?

Thanks

Trudy P Claspill · Answer

Hello @Digvijay Singh Gehlot

The native Clone process does not allow you to make changes to the issues being created so it is not possible to add any sort of flag to the issues to indicate more layers need to be cloned.

You could potentially create a process that uses Automation Rules rather than the native Clone feature to initiate the cloning of the Portfolio Epic and all its descendants. That would not block the users from using the native feature, though, so you could still end up with cloned hierarchies that are incomplete.

You could potentially add a "Clone" workflow transition for the Feature Portfolio, and build a post function script for it to execute that would accomplish the recursive cloning. Again, that would not block users for using the native Clone function and creating incompletely cloned hierarchies.

The simplest solution would be a third party app such as the one suggested by @Olivier_OSTConsulting . There are several cloning apps available from the Atlassian Marketplace. Here is a search to help you get started looking at them.

https://marketplace.atlassian.com/search?query=clone&product=jira&hosting=cloud

Olivier_OSTConsulting · Answer

Hi @Digvijay Singh Gehlot

If you're open to using Atlassian Marketplace apps, I’d recommend checking out our app Easy Clone for Jira Cloud.

It's specifically designed to help with cloning issue hierarchies like the one you described (Portfolio Epic > Feature > Task > Subtask) and can save time by replicating entire structures in just a few clicks.

Best regards,

Olivier