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 products 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.
Environment
Jira Service Management Cloud.
Solution
Create the rule and update the automation scope:
The Scope of the rule will determine the projects 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 projects and add the source project and destination.
Building the automation
1 - Select the automation trigger according to your project requirements.
2 - Select the “Clone Issue” action.
Fill in the destination project and the ticket issue type.
Edit the summary and add the field that will be cloned to the new project.
3 - Create a branch to update the request type in the destination project.
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.
References:
Was this helpful?