Can a form and its content be copied over when cloning a ticket?

[Cecilia Rodriguez]

Some tickets in our Service Management project are cloned and moved into Software Development projects.
When cloning, we haven’t found a way to copy the form from the original ticket into the new one.

Is there any way to export a form and re-import it into the new ticket? Or a way for the form (with its data) to persist in the cloned issue?

[Bill Sheboy]

Hi @Cecilia Rodriguez -- Welcome to the Atlassian Community!

How are you cloning the work item / ticket?

When doing that with an automation rule, you could use the Copy Forms action to attach the forms.

Kind regards,
Bill

[Marc - Devoteam]

HI @Cecilia Rodriguez 

@Bill Sheboy is right here, this can't be done with the Clone Work Item action.

In the automation rule, branch the rule based on most recent created issue and then copy the form.

[Bill Sheboy]

Hi @Cecilia Rodriguez 

Just following up to check if this answered your question.  If so, please consider marking this one as "answered".  That will help others with a similar need find solutions faster.  If not, please let the community know what help you need with the rule changes.

Thanks!

[Olha Yevdokymova_SaaSJet]

Hi @Cecilia Rodriguez 

In native JSM, forms and their responses don’t persist when you clone an issue — cloning only copies Jira field values, not the embedded form. There’s also no export/import option to move a form submission to another issue. That’s why your cloned Jira Software tickets lose the original structured form.

Native workaround (no apps):

• Map form questions to Jira fields so the values carry over during cloning.

• Or export the submitted form as a PDF/HTML attachment before cloning — this preserves the information but makes it static and non-editable.

If you want to keep the form structure and content in the cloned Software issue:
With Smart Forms for Jira (developed by my team), you can avoid this gap by:

• External sharing – Give customers or internal stakeholders a direct link to the form, even if the receiving project is Jira Software.

• Adding the Smart Form directly to the JSM request form so customers submit through it.

• When the JSM ticket is cloned or a related Software ticket is created, the same Smart Form (and its data) can be added to the cloned ticket.

• If needed, the form — or its saved draft — can be reopened and updated in the Software ticket, so more details can be added.

• This keeps the form live and editable in both tickets, so both teams always see the latest information in a structured view.

[Clara Belin-Brosseau_Elements]

Hi @Cecilia Rodriguez

To copy your issues from JSM to Jira including their forms, I can suggest trying our app Elements Copy & Sync.

 

Don't hesitate to check the documentation, it’s really quick and easy to set up.

The app is for free during 30 days (and it stays free under 10 users)