Copying fields from a form in a project to another project

[Claudia Riverin]

Hello! I am very beginner and I am trying to solve my problem.

I am not able to copy fields from a project to another one. Here is my scenario.

Request is made in project #1 with a form. 
Trigger to create ticket in project #2 is a selected option in the form in project #1.

That works correctly. 

But I need to copy all fields from the form in project #1 to the ticket in project #2. 
It seems I am not able to make it. Only one field is working out. 

Can someone explain me what I am doing wrong?

Thanks!

[Luka Hummel - codefortynine]

Hi @Claudia Riverin 👋

Jira automation can create the follow-up issue in project #2, but today it can’t bring over Jira Service Management forms and many other details. If you want the new ticket to look exactly like the original request —including all form answers, custom-field values, comments, attachments, watchers, even the current status—have a look at our app Deep Clone for Jira.

[Olha Yevdokymova_SaaSJet]

Hi @Claudia Riverin 

You're on the right track with the trigger setup between Project #1 and Project #2 — but I totally get the frustration with copying all form fields over.

With Jira’s native forms, you're limited because each form field must be mapped one-to-one with a Jira field — and that mapping doesn't always carry over smoothly between projects, especially if the fields aren't identical in both projects.

If you're open to trying an add-on, Smart Forms for Jira makes this process much smoother. Here's how:

✅ All forms are automatically available across all projects — no need to recreate them and forms can be used to create new issues or update existing ones
✅ When an issue is cloned or moved between projects, the form and its data stay attached, so you can move submitted detail between projects and even draft forms
✅ You can map multiple form fields to corresponding Jira fields — even combine fields into the same Jira field (like the Description)
✅ You can even update existing issues using forms or trigger status transitions after form submission

So instead of rebuilding or reconfiguring everything, Smart Forms helps keep form data structured and reusable across your Jira projects.

Let me know if you’d like a quick setup tip or an example workflow — happy to help!

[Marc - Devoteam]

Hi @Claudia Riverin 

Are the fields in the form linked to Jira fields, or just form fields?

If they are linked to Jira fields, are these fields on the create and edit screens of project #2?

[Claudia Riverin]

Hi Marc. Thanks for the reply.

Fields are linked, yes.

But good question for the screens. I'll have a look. But project #1 is a team-managed and project #2 is company-managed. Will it work still? 

[Claudia Riverin]

So, yes. fields are in the screens of project #2... :(

[Marc - Devoteam]

HI @Claudia Riverin 

If you created custom fields within Team Managed projects, they cannot be used in other projects. They are accessible only in the Team Managed project where they were created.

Custom fields that are created for use in Company Managed projects are created in a global location intentionally so that they can be shared also within Team management projects.

[Claudia Riverin]

Hi @Marc - Devoteam 

Thanks for your return.

Indeed. My fields are created in a global location. I've used all linked fields from my global custom fields to the team-managed form. But only one is copying. The others not. I really don't understand why. 

[Marc - Devoteam]

HI @Claudia Riverin 

Check the contexts set on your custom fields.

[Claudia Riverin]

Hi @Marc - Devoteam 

They all have the same set up as the custom field that copy correctly.

:( 

[Marc - Devoteam]

Hi @Claudia Riverin 

What if you change the trigger of the rule to form submitted and base this on the form used in the 1st request.

I think it's a timing issue, the 1st issue is still creating when rule 2 is also running based on issue creation.

Can you show the field config of a custom field as well?

[Claudia Riverin]

I've changed the trigger for form submitted. This part is working.
But my problem with that is I cannot associate ticket together, because Form trigger is only working in Single project..

And now, I have duplicates in my fields...

Sorry to bother you with that. Like I said, I'm green... ;) 

---

Here is a field config for two of the custom field.

Sorry it's in french.

[Marc - Devoteam]

Hi @Claudia Riverin 

The problem then is that 2 rules firing on issue creation run parallel at the same time, So you need to have the rule that copies the info to a new ticket based on a timer or based upon an transition?

What is you set the trigger back to issue created and then add a delay action for let's say 30 seconds, so do this action direct after the trigger, before the "if"

What is the result then?

[Claudia Riverin]

Hi @Marc - Devoteam 

I will have to check on that in a week. I'm off on holiday, didn't have to look. 

Thanks soooo much for your help!

[Claudia Riverin]

@Marc - Devoteam Just found out that a new menu appeared in my project: FIELDS! OMG! So I have to add my global Jira field in my project from there, and after I can link them. It seems working out! Yeah! 

I'll do some tests.

Thanks so much for your help!

[Marc - Devoteam]

Hi @Claudia Riverin 

Please accept my answer as a solution, if my answer helped to solve your request.

This will help other community member trying to solve the same.

P.S. If the answer is very valuable to you, please share some kudos.