How to clone an issue and update the request type using Automation in JSM Cloud

Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.

Summary

When cloning an issue in JSM Cloud Issue using automation for Jira, the request type is not automatically updated in the cloned ticket.

Solution

Create the rule and update the automation scope:

The Scope of the rule will determine the spaces it runs across. It can only be edited from the global administration settings.

  • Go to Settings > System > Global Automation.

  • Select the “Create rule” button > Rule details.

  • In the scope, select Multiple spaces, then add the source and destination spaces.

Building the automation

1 - Select the automation trigger according to your space requirements.

2 - Select the “Clone Issue” action.

  • Fill in the destination space and the ticket issue type.

  • Edit the summary and add the field that will be cloned to the new space.

3 - Create a branch to update the request type in the destination space.

Before saving the rule, confirm that the destination request type's underlying issue type matches the issue type used in the Clone Issue action's destination project — catching this at rule configuration time avoids the runtime error described in the note about request type mismatches.

  • Add a new component > Branch rule / related issues

  • In the Type of related issues > Select Most Recently Created Issue.

  • Select Next > Add a new action: Edit Request type.

  • Choose the request type for the cloned issue.

  • Save the rule.

Each request type is based on an issue type. If the chosen request type isn't based on the current issue type, or if the issue type changes, this action will result in an error.

(Auto-migrated image: description temporarily unavailable)

If clones can be created in quick succession (for example, multiple issues cloned within the same automation execution window), test that the 'Most Recently Created Issue' branch reliably picks the correct clone and not a different, concurrently-created issue before relying on this in a high-volume project.

References:

Updated on August 11, 2026

Still need help?

The Atlassian Community is here for you.