nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Screenshot 2025-05-09 at 10.19.03 AM.png Screenshot 2025-05-09 at 10.17.11 AM.png

Screenshot 2025-05-09 at 10.18.14 AM.png

Can someone explain me what I am doing wrong?

Thanks!

Accepted answers

All comments

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...

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.

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.

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!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management