Assets - Bulk clone objects to a different object type or schema

[Trish Le]

Following this Atlassian guide on how to bulk clone objects into a different object type

https://confluence.atlassian.com/jirakb/assets-bulk-clone-objects-to-a-different-object-type-or-schema-1206560732.html#:~:text=Currently%2C%20in%20the%20Jira%20Service,object%20type%20as%20the%20original.

The guide worked, but in my test Asset environment, I have over 190 applicable objects to be cloned, and the automation only cloned 50 of them. 

Is that a limitation of this automation rule? 

[Anthony]

FYI - two things:

- if you have objects that are nested, you will need to use "objectType in objectTypeAndChildren("<enter the object type>")

- if you have an attribute with spaces, you need to include those spaces in the automation field i.e. if attribute is Asset Tag ID, it would be written as {{object.Asset Tag ID}}

[Fabian Lim]

Hi @Trish Le

The other option is to export the csv spreadsheet of the objects you want to clone.  Then use an Asset CSV Import to populate into the new object or schema.  

Regards,

Fabian

[Trish Le]

Slight issue with that. I have an owner/user field using the user object. When you export the objects, the owner column will display the name of the person that owns the device. But to import and map the attribute of owner into Asset you will need their Jira/Atlassian account ID, which is hard to get. You can get it by making API calls and then tacking that ID back onto the CSV file. But if something more direct I would prefer that. 

Thank you. 

[Fabian Lim]

Agree, it's a pain. 

For a client we had to import all the owners.  Then grab another spreadsheet with users and the account IDs from the user management admin.  Finally use a excel Vlookup to match the correct acount ID to the owner field.  It worked, but it requires some manipulation.