Clone EPIC & Stories to New Epic and link New Stories via Automation

[Melissa Lato]

I have been trying to write a manual automation rule to clone an EPIC (or the selected issue) with all its sub tasks and then link them all as they were in the original EPIC:

I have tried many variations of this but all the Stories seem to stay linked to the original EPIC. I feel like I am so close that someone hopefully will be able to confirm the final steps for linking them up.

Thanks in advance.

[Andy Heinzer]

Jira Cloud does not have single project exports nor does it have single project imports.   It is possible to move this data to another cloud instance, however it's much easier to do if you want to duplicate ALL the jira data in that Cloud site, and not just this one project.   If that explains your use case here, please see How to restore a JIRA Cloud application backup into another JIRA Cloud application

However if you have other projects in your Cloud site that you do not want to provide to your client/customer, then the number of steps is considerably longer, but achievable. Essentially what you would need to do would be to create a backup of your Jira Cloud data, and then restore it to another Jira instance (this could be a Cloud or Server installation).  From this restored copy, you would then need to delete all the projects that you don't want to provide to your client.   By doing this on the restored clone, you can then create a new XML backup and provide that, along with the appropriate attachments to your client.  With that data they can then import this complete Jira XML backup into a new Cloud site.

Migrating from Jira Cloud to Server applications - could be used in this case, but if you're only deleting other projects in the backup, you don't have to go to Server.   You could do this in another cloud site.   We frequently see customers that want to merge Jira sites, which requires you to go to Server in order to be able to do single project imports.   Since it doesn't sound like that applies here, it's probably much easier to just copy your Jira cloud into another test cloud site first, and then remove all the extra data that you don't want this client to have, generate a new backup and provide that data to them.

[JVHE]

Thank you for your feedback.  This explanation must be sufficient for us.

[Andy Heinzer]

Glad to hear that helped.  If this resolved your question, please click the checkmark to accept this answer as a solution.  This can in turn then help other users that might later have the same question.