Jira automation. make a clone of a ServiceDesk ticket to another Project including form

Question

Hi I'm new here, so perhaps this question is already asked.
I created two different automation rules, to clone a SD ticket which has a form attached to another project.
I managed to copy the form fields to the other project, but the values the customer entered are gone after the clone action, so only the empty form is visible.
What am I missing?

Luka Hummel - codefortynine · Answer

Hi @Albert-Jan

If you think we can do better to help convince your admin you can always contact us here.  All feedback is welcome :)

Albert-Jan · Answer

Hi @Luka Hummel - codefortynine

Thnx for your reaction. I already did some reading on Deep Clone, however it's quite hard to convince the Jira admins to add this to the apps in Jira.

Luka Hummel - codefortynine · Answer

Hi @Albert-Jan and welcome to the community!

It sounds like you're trying to clone a Jira Service Management (JSM) ticket to another project while ensuring that the form fields, along with the values entered by the customer, are retained. Jira Automation has some limitations when cloning JSM tickets, especially when it comes to forms and their associated data.

For a more reliable and flexible cloning solution, I recommend using our app Deep Clone for Jira. Deep Clone allows you to clone issues across projects, including all relevant fields, forms, attachments, comments, and even issue links.

Some key advantages of Deep Clone for Jira in your scenario:

* Full Issue Cloning: Copies all issue details, including custom fields and attachments.
* Bulk Cloning: Clone multiple tickets at once if needed.
* Cross-Project Cloning: Seamlessly move issues between projects while maintaining data integrity.

You can find more on cloning attached forms here.