Jira Service Mangement (JSM) forms can be a powerful tool for gathering information from customers and sharing it with your agents but when it comes to sharing forms between projects, your options are more limited. Jira automation can copy forms within the project the form belongs to but if you need to pass a form off to another team, the automations will silently fail and not copy the information. There are a few workarounds that allow you to copy the PDF of the form but these lose much of the forms functionality that makes forms so useful. Luckily there is a way to copy forms between different projects by using a combination of Jira automation and the REST API.

Understanding the Forms Copy API

Atlassian provides a REST API endpoint specifically designed for copying forms between issues and projects. Here’s the endpoint:

POST https://api.atlassian.com/jira/forms/cloud/{cloudId}/issue/{sourceIssueIdOrKey}/form/copy/{targetIssueIdOrKey}

Here is a break of the variables above:

• cloudId: Your Atlassian cloud instance identifier (we’ll show you how to find this)
• sourceIssueIdOrKey: The issue containing the form you want to copy
• targetIssueIdOrKey: The destination issue where you want to paste the form

Step 1: Find Your Cloud ID

Your Cloud ID is different from your Organization ID, and you’ll need it for the API call to work properly.

To find your Cloud ID:

1. Navigate to your Atlassian Admin page (found in the app switcher on the top left)
2. Select your site
3. Under Sites > on the left, select your site again.
4. Look at the URL in your browser’s address bar and grab the alphanumberic value after the /s/

You’ll see something like: https://admin.atlassian.com/s/abc123def-4567-89gh-ijkl-mnopqrstuvwx/jira-service-management/portal-only-customers f03047d3-249f-4cfb-893a-5d72864af428

The Cloud ID is the long alphanumeric string between /s/ and jira-service-management/. In this example, it would be abc123def-4567-89gh-ijkl-mnopqrstuvwx.

Step 2: Identify Your Form ID

Each form in JSM has a unique Form ID. You’ll need this to specify which form to copy. This used to be tough to find but now there is a fast way to get this.

1. Navigate to the forms section on your JSM project
2. Next to the form you want to copy, select the ... button and select Copy form ID.

This is your Form ID. Keep it handy—you’ll need it in the next step.

Step 3: Create Your Automation Rule

For this to function, you will need to make this as a global or multi-project rule.

1. Go to System → Automations
2. Click Create rule
3. Select Work Item Transitioned as your trigger
4. Select the status that will cause the trigger.

Adding the API Call

Now we’ll configure the automation to call the Forms API. In this example we are assuming that the issue we want to copy this form to is linked to the work item already. We make use of the smart values {{issue.key}} to specify the trigger work item and {{issue.issuelinks.inwardIssue.key}} to specify the destination work item.

1. Click Add component → Send web request
2. Configure the web request with these settings:

Web request URL:

https://api.atlassian.com/jira/forms/cloud/YOUR_CLOUD_ID/issue/{{issue.key}}/form/copy/{{issue.issuelinks.inwardIssue.key}}

Replace YOUR_CLOUD_ID with the Cloud ID you found in Step 1.

HTTP Method: POST

Web request body: Custom data

{
  "formId": "{{issue.forms.cf638d8b-0498-4b80-8fb1-f547dc769421}}"
}

Replace cf638d8b-0498-4b80-8fb1-f547dc769421 with your Form Template ID from Step 2.

Headers:

• Content-Type: application/json
• Authorization: Bearer YOUR JIRA API KEY

Step 4: Test Your Automation

Before deploying this to production, test it thoroughly:

1. Create a test issue with your form filled out
2. Create or link a second issue that will receive the copy
3. Transition the source issue to trigger your automation rule
4. Check the target issue to verify the form was copied correctly
5. Review the automation audit log for any errors

Common Use Cases

This automation technique is particularly valuable for:

Cross-Project Workflows

If your organization routes requests between different service desks (e.g., from IT to Facilities), preserve the original form responses throughout the journey.

Approval Processes

Create approval issues that include all the original request information without requiring approvers to reference multiple tickets.

Escalation Workflows

When escalating issues to higher support tiers, ensure specialist teams have access to all original form data.

Note, both projects need to be JSM projects. Forms are not supported in Jira Software yet.

Need Help with Jira Automation?

At Stalworx, we specialize in creating custom Jira automation solutions that streamline your workflows and eliminate repetitive tasks. From simple form copying to complex multi-step processes, we can help you unlock the full potential of Jira Service Management.

Contact us today to learn how we can optimize your Atlassian tools and transform your team’s productivity.