Cloning from JSM to JWM Sub-Tasks are not cloning

[Sara Palmitessa]

I created an Automation rule that clones an Epic from JSM to JWM.  The Epic does get cloned when a specific type of request is created.  There are two pieces that are not getting cloned - the Form and the Sub-Tasks.  I have tried to look into Deep Clone, but the problem is that it does not allow me to decide which requests and Epics go into particular projects.  I have many different request types (set up as an Epic in JSM) and they each go into different projects.

How do I move my form and sub-tasks automatically? I have also tried to create a rule in JWM that when an issue is moved, it creates sub-tasks, but that did not work either, mainly I think because it was cloned and not moved but I did not see just a move option.

[Julien Peyrade _ Elements]

Hello @Sara Palmitessa  

If you don't mind testing an add-on, Elements Copy & Sync lets you do exactly that.

Full disclosure, I'm the Product Manager of the app.

With our app, you will be able to clone Epics with all their issues, including subtasks and forms, and keep the hierarchy.

It is as easy as clicking on two options, which are explained in our tutorials:

• clone full Epics
• clone issues and subtasks as once

The app is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.

Kind regards,

Julien

[Sara Palmitessa]

Hi @Julien Peyrade _ Elements  I would be happy to try that out.  Any chance we can get on a call today and you help me with this? I have been trying to figure out a solution for almost 2 months and am going nuts! I will try the tutorials you mentioned but would appreciate a call if possible to answer additional questions.

[Julien Peyrade _ Elements]

If you don't mind, could you create a support ticket? Our team will be happy to answer any of your question, even the hardest. :)

Unfortunately I'm unable to take any call before next week.

[Umer Sohail _K15t_]

Hey @Sara Palmitessa, thanks for the question. 

This is Umer, PMM for Backbone Issue Sync for Jira. From what I gather, you want your epic to be automatically cloned/copied from your JSM to JWM along with the form (an attachment?) and sub-tasks.

Using Jira automations work well for a while, but they are difficult to figure out and maintain when things get a bit more complicated.

If you want to automatically copy epics from the JSM project to JWM, along with comments, attachments, and custom fields, you might want to look for a specialized Jira Issue Sync app, like Backbone Issue Sync for Jira. 

Using Backbone, you can sync Jira issues and their corresponding data between two Jira projects without leaving your own Jira project. And you get complete control over which epics (and sub-tasks) to sync with a particular project.  

In case you're interested in discussing your particular use case, feel free to schedule a free demo or try Backbone for free for the first 30 days!  

[Nic Brough -Adaptavist-]

Moving issues between projects, especially from JSM projects, is a bad practice and is not something you should be doing as part of a standard process. 

Automation, and the advanced clone apps you can find in the marketplace do not do it because moving issues needs checking that the data on the issue is valid for the new project and asking people to change it if it does not.

When you clone an issue, the system clones just the issue.  If it has forms or sub-tasks, they do not get cloned, because they are not the issue being replicated.

I strongly recommend you look at why you are trying to do this, it is not a good thing, and the desire to do it suggests you have a broken process.