Bulk Clone Assets Objects Across Schemas and Types in JSM Cloud

Summary

In the Jira Service Management Assets tool it is not possible to move objects to a different object type.

Additionally, the Clone action can only create objects in the same object type as the original.

With the help of Automation, we can create a process to bulk clone objects to a different object type or schema. This will save you some time when it is necessary to move objects, so you won't have to manually recreate all objects.

Important Note on this Workaround:

Some things to keep in mind:

• The object key will not be the same on the cloned objects.

  • Assets object fields that have the original objects stored in them might need to be updated with the new ones. The following article can help you bulk update existing values on the Assets fields:

    • How to bulk update Assets Object custom fields via External System Import

• You might need to create a new Assets object custom field or adjust an existing one to show the objects created via this process.

  • Set up the Assets objects custom field

Solution

Creating the ObjectType

Ensure that the target object type has all of the attributes that the original object type has.

Example:

• Navigate to your OldObjectType.

• Select to see the Attributes.

• OldObject has the Warranty and User attributes (aside from the default ones) in our example:

  

• Add the same attributes in the NewObject:

Creating the Automation Rule

The next step is to create the automation rule to clone/move the objects from OldObject to NewObject.

Go to System (⚙) > Global Automation and start a new rule with the following components:

• Scheduled Trigger: We use the scheduled trigger so we can execute the rule as needed. The schedule itself is not really important, but be aware that, depending on how you configure it, the rule might be triggered again. Ideally, you should disable the rule after using it, and enable it again in case you need to use it in the future.

  

• Branch on AQL: Select the schema where the objects reside and use the "Query" field to add an AQL that will narrow down the results.

  • Example: filter by adding "objecttype = OldObject". Feel free to add as many AQL statements as needed for your use case. For more information on how to build AQL statements, please check the Use Assets Query Language (AQL) article.

    

• Create Object:

  • Select the target object schema and also the target object type where the objects will be created.

  • Select all attributes that will be copied over to the new objects and use the {{object.AttributeName}} smart value. Don't forget to replace <AttributeName> with the actual name of the attributes from the old objects.

    

• Name your automation rule and publish it by clicking on Turn it on.

• Run the rule by clicking on the Run Rule button.

Result

The objects should be copied over to the new object type and schema.